How do I install the Opensrc skill?

Run npx skillmds@latest add canvascoding/opensrc in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Opensrc safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Opensrc?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Opensrc free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Opensrc?

canvascoding (@canvascoding) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Opensrc by canvascoding — Agent Skill

Name: Opensrc
Author: canvascoding

Opensrc

Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for", "read the source of", "how does X work internally", "get the implementation of", "opensrc path", or any task requiring access to dependency source code beyond types and docs.

canvascoding e811982 7 files · 30.4 KB Updated Sep 17, 2026

File contents

Source Code Fetching with opensrc

Fetches dependency source code so agents can read implementations, not just types. Clones repositories at the correct version tag and caches them globally at ~/.opensrc/.

Core Pattern

rg "parse" $(opensrc path zod)
cat $(opensrc path zod)/src/types.ts
find $(opensrc path zod) -name "*.test.ts"

opensrc path <pkg> prints the absolute path to cached source. If not cached, it fetches automatically. Progress goes to stderr, path to stdout, so $(opensrc path ...) works in subshells.

Fetching Source Code

opensrc path zod
opensrc path pypi:requests
opensrc path crates:serde
opensrc path facebook/react

# Multiple packages at once
opensrc path zod react next
opensrc path pypi:requests pypi:flask
opensrc path crates:serde crates:tokio

# Specific versions
opensrc path zod@3.22.0
opensrc path pypi:flask@3.0.0
opensrc path owner/repo@v1.0.0
opensrc path owner/repo#main

Version Resolution

For npm packages, opensrc auto-detects the installed version from lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock). Use --cwd to resolve from a different project:

opensrc path zod --cwd /path/to/project

For PyPI and crates.io, explicit versions or latest are used. For repos, use @ref or #ref to pin a branch, tag, or commit.

Managing the Cache

Source is cached globally at ~/.opensrc/ (override with OPENSRC_HOME).

opensrc list                     # show all cached sources
opensrc list --json              # JSON output

opensrc remove zod               # remove a package
opensrc remove facebook/react    # remove a repo

opensrc clean                    # remove everything
opensrc clean --npm              # only npm packages
opensrc clean --pypi             # only PyPI packages
opensrc clean --crates           # only crates.io packages
opensrc clean --packages         # all packages, keep repos
opensrc clean --repos            # all repos, keep packages

When to Fetch Source

Fetch source when you need to:

Understand internal behavior that types don't reveal
Debug unexpected library behavior
Learn patterns from well-known implementations
Verify how a function handles edge cases

Don't fetch source for simple API usage questions that docs or types can answer.

---name: opensrcdescription: Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for", "read the source of", "how does X work internally", "get the implementation of", "opensrc path", or any task requiring access to dependency source code beyond types and docs.---# Source Code Fetching with opensrcFetches dependency source code so agents can read implementations, not just types. Clones repositories at the correct version tag and caches them globally at `~/.opensrc/`.## Core Pattern```bashrg "parse" $(opensrc path zod)cat $(opensrc path zod)/src/types.tsfind $(opensrc path zod) -name "*.test.ts"````opensrc path <pkg>` prints the absolute path to cached source. If not cached, it fetches automatically. Progress goes to stderr, path to stdout, so `$(opensrc path ...)` works in subshells.## Fetching Source Code```bashopensrc path zodopensrc path pypi:requestsopensrc path crates:serdeopensrc path facebook/react# Multiple packages at onceopensrc path zod react nextopensrc path pypi:requests pypi:flaskopensrc path crates:serde crates:tokio# Specific versionsopensrc path zod@3.22.0opensrc path pypi:flask@3.0.0opensrc path owner/repo@v1.0.0opensrc path owner/repo#main```### Version ResolutionFor npm packages, opensrc auto-detects the installed version from lockfiles (`package-lock.json`, `pnpm-lock.yaml`, `yarn.lock`). Use `--cwd` to resolve from a different project:```bashopensrc path zod --cwd /path/to/project```For PyPI and crates.io, explicit versions or latest are used. For repos, use `@ref` or `#ref` to pin a branch, tag, or commit.## Managing the CacheSource is cached globally at `~/.opensrc/` (override with `OPENSRC_HOME`).```bashopensrc list # show all cached sourcesopensrc list --json # JSON outputopensrc remove zod # remove a packageopensrc remove facebook/react # remove a repoopensrc clean # remove everythingopensrc clean --npm # only npm packagesopensrc clean --pypi # only PyPI packagesopensrc clean --crates # only crates.io packagesopensrc clean --packages # all packages, keep reposopensrc clean --repos # all repos, keep packages```## When to Fetch SourceFetch source when you need to:- Understand internal behavior that types don't reveal- Debug unexpected library behavior- Learn patterns from well-known implementations- Verify how a function handles edge casesDon't fetch source for simple API usage questions that docs or types can answer.

Frequently asked questions