LabscoMCP early access ↗
REPO PACKAGECOMMUNITY

vercel-labs opensrc

vercel-labs · publisher2,759 GitHub starsApache-2.0 · Listed as freegithub.com/vercel-labs/opensrc

LABSCO SUMMARY

Summary

opensrc is a single skill wrapping one CLI: fetch a dependency's real source code so an agent reads the implementation instead of guessing from its types or docs.

The skill runs opensrc path <package> (plain for npm, or prefixed pypi: for PyPI, or a crates.io or GitHub reference) against that package's registry, fetches the source the first time it's asked for, and caches it locally so every later call returns instantly. From there, an ordinary shell command does the actual reading: the README's own examples are rg searching over the cached path, cat on one specific file, and find filtered by extension — the skill is the fetch-and-cache step, not a search tool in its own right.

There is exactly one skill in this repository: it needs the opensrc CLI installed globally (npm install -g opensrc), but no account, API key, or MCP server. That is also the whole of what the repository offers as a skill — the rest of the monorepo is the CLI's own Rust implementation (packages/opensrc/cli, built and tested with Cargo) and a separate Next.js documentation site, neither of which is packaged as a skill of its own.

READ MORE

Who this is for.

Anyone whose agent keeps citing a dependency's public types or README instead of its actual behavior gets, with this one skill, a local copy of the real source to grep or read directly. The description names npm, PyPI, and crates.io by name; it says nothing about which languages the fetched source itself favors, so a Python-only or Rust-only workflow gets exactly the same single skill as everyone else.