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.
Best for Debugging complex dependenc…Works with GitHubLow risk
⌘source
- author
@remorses- repo
- remorses/kimaki
- language
- TypeScript
★1kstars
77forks
Apr 18, 2026
✦overview.md
Key Features
- ·Fetches dependency source code from npm, PyPI, crates.io, and Git repositories
- ·Caches source globally at ~/.opensrc/ for reuse
- ·Returns absolute path to source for use in shell commands
- ·Supports fetching multiple packages and specific versions
- ·Automatically fetches if source is not already cached
Use Cases
- →Understanding internal library behavior when debugging an issue
- →Reading implementation details not covered by type definitions or documentation
- →Exploring how a specific version of a package is built
- →Running grep or find commands across dependency source code
Best for
- ✓Debugging complex dependency issues
- ✓Library authors analyzing dependencies
Not ideal for
- !Tasks requiring only API documentation or type definitions
- !One-off analysis of proprietary or private packages not on supported registries
FAQs
name
opensrc
description
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.
allowed-tools:Bash(opensrc:*)
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:
$install
1-click copynpx skills add remorses/kimaki --skill opensrcSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
5/ 5
excellentVery clear and well structured, with almost no room for misunderstanding.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
5/ 5
very highHighly actionable with clear, concrete steps that an agent can follow directly.