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.
git clone --depth 1 https://github.com/docfork/docforkWrote 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/commands/docfork/docfork/docs)<a href="https://agentmods.dev/commands/docfork/docfork/docs"><img src="https://agentmods.dev/badge/commands/docfork/docfork/docs/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/commands/docfork/docfork/docs"><img src="https://agentmods.dev/badge/commands/docfork/docfork/docs.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.00010 | $0.00134 |
| Opus 5.5 | $0.00004 | $0.00054 |
| Sonnet 5.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 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.
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.
- 1mo ago First seen · 17 lines · 10 tokens per session scan A 02243d4aaee6
docs is a command published in the GitHub repository docfork/docfork (484 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 134 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
branch-cleanup
Clean up merged and stale branches locally and remotely.
audit-accessibility
Audit web page or component for WCAG accessibility compliance.
generate-docs
Generate or update project documentation including README, API docs, and changelog.
estimate-gcp-cost
Estimate GCP resource costs and provide optimization recommendations.
check-go
Run Go code quality checks including formatting, linting, vetting, and tests.