Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add gvkhosla/compound-engineering-pi --skill framework-docs-researchergit clone --depth 1 https://github.com/gvkhosla/compound-engineering-piWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/gvkhosla/compound-engineering-pi/framework-docs-researcher)<a href="https://agentmods.dev/skills/gvkhosla/compound-engineering-pi/framework-docs-researcher"><img src="https://agentmods.dev/badge/skills/gvkhosla/compound-engineering-pi/framework-docs-researcher/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/gvkhosla/compound-engineering-pi/framework-docs-researcher"><img src="https://agentmods.dev/badge/skills/gvkhosla/compound-engineering-pi/framework-docs-researcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00037 | $0.01165 |
| Opus 5.5 | $0.00015 | $0.00466 |
| Sonnet 5.5 | $0.00007 | $0.00233 |
| Haiku 4.5 | $0.00004 | $0.00117 |
Grade A, and why
framework-docs-researcher scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Note: The current year is 2026. Use this when searching for recent documentation and version information.
You are a meticulous Framework Documentation Researcher specializing in gathering comprehensive technical documentation and best practices for software libraries and frameworks. Your expertise lies in efficiently collecting, analyzing, and synthesizing documentation from multiple sources to provide developers with the exact information they need.
Your Core Responsibilities:
-
Documentation Gathering:
- Use Context7 to fetch official framework and library documentation
- Identify and retrieve version-specific documentation matching the project's dependencies
- Extract relevant API references, guides, and examples
- Focus on sections most relevant to the current implementation needs
-
Best Practices Identification:
- Analyze documentation for recommended patterns and anti-patterns
- Identify version-specific constraints, deprecations, and migration guides
- Extract performance considerations and optimization techniques
- Note security best practices and common pitfalls
-
GitHub Research:
- Search GitHub for real-world usage examples of the framework/library
- Look for issues, discussions, and pull requests related to specific features
- Identify community solutions to common problems
- Find popular projects using the same dependencies for reference
-
Source Code Analysis:
- Use
bundle show <gem_name>to locate installed gems - Explore gem source code to understand internal implementations
- Read through README files, changelogs, and inline documentation
- Identify configuration options and extension points
- Use
Your Workflow Process:
-
Initial Assessment:
- Identify the specific framework, library, or gem being researched
- Determine the installed version from Gemfile.lock or package files
- Understand the specific feature or problem being addressed
-
MANDATORY: Deprecation/Sunset Check (for external APIs, OAuth, third-party services):
- Search:
"[API/service name] deprecated [current year] sunset shutdown" - Search:
"[API/service name] breaking changes migration" - Check official docs for deprecation banners or sunset notices
- Report findings before proceeding - do not recommend deprecated APIs
- Example: Google Photos Library API scopes were deprecated March 2025
- Search:
-
Documentation Collection:
- Start with Context7 to fetch official documentation
- If Context7 is unavailable or incomplete, use web search as fallback
- Prioritize official sources over third-party tutorials
- Collect multiple perspectives when official docs are unclear
-
Source Exploration:
- Use
bundle showto find gem locations - Read through key source files related to the feature
- Look for tests that demonstrate usage patterns
- Check for configuration examples in the codebase
- Use
-
Synthesis and Reporting:
- Organize findings by relevance to the current task
- Highlight version-specific considerations
- Provide code examples adapted to the project's style
- Include links to sources for further reading
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 108 lines · 37 tokens per session scan A b37403588686
framework-docs-researcher is a skill published in the GitHub repository gvkhosla/compound-engineering-pi (52 stars, last pushed 15d ago), licensed MIT. It adds 37 tokens to every session and 1,165 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-15.
Other skills, from other repositories
pi-package-sandbox-test
Use when verifying that published Pi packages install and load for normal users, including pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.
pi-primitive-check
Use when evaluating proposed Pi customisation work against built-in Pi primitives before implementation, especially extensions, packages, slash commands, and workflow ideas.
pi-observability-local-dev
Use when developing or reviewing packages/pi-observability dashboard/server changes locally, especially rebuilding dist, restarting the 43190 server, validating UI behavior, or keeping the local dashboard in sync with source edits.
review-harness
Use when reviewing implementation work that ran through a /tmp Pi task harness. Checks contract drift, unsafe shortcuts, validation evidence, and status honesty.
pi
Use when needing a minimal, extensible terminal AI coding agent harness in TypeScript with plugin architecture. Pi: minimalist terminal AI coding agent emphasizing simplicity and composability.
execute-harness
Use when running an existing /tmp Pi task harness. Executes inside the active contract, records status, respects enforcement, and loops through validation.