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 agentmods add commands/docfork/docfork/docsgit clone --depth 1 https://github.com/docfork/docforkWhat 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 | $0.00010 | $0.00134 |
| Opus 5 | $0.00005 | $0.00067 |
| Sonnet 5 | $0.00002 | $0.00027 |
| Haiku 4.5 | $0.00001 | $0.00013 |
Grade A, and why
docs 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 yesterday.
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.
What it actually says
Fetch current documentation using Docfork and return a direct answer with runnable code examples.
Examples
/docfork:docs react server components
/docfork:docs nextjs app router middleware
/docfork:docs supabase row level security
/docfork:docs zod nested object validation
Use docfork:search_docs with the library name, extract owner/repo from result URLs for follow-up calls, then docfork:fetch_doc for full content. Search results are summaries only.
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.
- yesterday First seen · 17 lines · 10 tokens per session scan A 02243d4aaee6
docs is a command published in the GitHub repository docfork/docfork (488 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 134 once invoked, about $0.0001 per session on Opus 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-08-30.
Other commands, from other repositories
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
generate-docs
Generate or update project documentation including README, API docs, and changelog.
estimate-azure-cost
Estimate Azure resource costs and provide optimization recommendations.
commit
Act as a senior software engineer to commit changes to the repository in non-interactive modes ONLY, using the following template.
validate-pipeline
Validate data pipeline configuration and data quality rules.
aidd-churn
Rank files by hotspot score to identify prime candidates for refactoring before PR review.