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 ToruAI/toru-claude-agents --skill cc-docsgit clone --depth 1 https://github.com/ToruAI/toru-claude-agentsWrote 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/toruai/toru-claude-agents/cc-docs)<a href="https://agentmods.dev/skills/toruai/toru-claude-agents/cc-docs"><img src="https://agentmods.dev/badge/skills/toruai/toru-claude-agents/cc-docs.svg" alt="Measured on agentmods" 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.00041 | $0.00691 |
| Opus 5 | $0.00020 | $0.00345 |
| Sonnet 5 | $0.00008 | $0.00138 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
cc-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 8d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Documentation
Answer questions about Claude Code from the official documentation, fetched at the moment you need it. Do not answer from memory: this product ships changes weekly, and a confidently wrong answer about a hook event or a manifest field costs more than a fetch.
How to Use
Fetch the page that covers the question with WebFetch. Start from the overview only if
you need to find your way around; otherwise go straight to the relevant page.
| Topic | URL |
|---|---|
| Overview / index | https://code.claude.com/docs/en/overview |
| Skills | https://code.claude.com/docs/en/skills |
| Hooks — guide | https://code.claude.com/docs/en/hooks-guide |
| Hooks — full reference | https://code.claude.com/docs/en/hooks |
| Subagents | https://code.claude.com/docs/en/sub-agents |
| MCP | https://code.claude.com/docs/en/mcp |
| Plugins — guide | https://code.claude.com/docs/en/plugins |
| Plugins — reference | https://code.claude.com/docs/en/plugins-reference |
| Plugin marketplaces | https://code.claude.com/docs/en/plugin-marketplaces |
| Slash commands | https://code.claude.com/docs/en/slash-commands |
| Settings | https://code.claude.com/docs/en/settings |
| CLI reference | https://code.claude.com/docs/en/cli-reference |
If a URL 404s, the docs have been reorganised — fetch the overview and follow its navigation rather than guessing a new path.
Verify against the live CLI where you can. For anything about plugins, hooks or settings, the installed binary is a second source of truth and it cannot be out of date:
claude plugin validate <path> # what the schema actually accepts, warnings included
claude plugin --help # current subcommands
claude --help # flags
When the docs and the CLI disagree, trust the CLI and say so in your answer.
When to Use
- Someone asks "how do I…" about a Claude Code feature
- You are about to write a hook, skill, subagent, plugin manifest or settings block
- You need to check whether a field, event or flag actually exists
- Something behaves differently than expected and you need the spec, not a guess
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.
- 8d ago First seen · 62 lines · 41 tokens per session scan A 94b27ec34fcc
cc-docs is a skill published in the GitHub repository ToruAI/toru-claude-agents (15 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 691 once invoked, about $0.0002 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 skills, from other repositories
ln-11-plan-reviewer
Reviews an implementation plan against repository evidence before execution; identifies missing decisions and risks. Not for completed-code review.
ln-12-delivery-reviewer
Reviews a completed change for regressions, unmet acceptance, and release risks. Not for whole-codebase audits or repairs.
ln-23-test-suite-auditor
Audits existing tests for meaningful coverage, trustworthy oracles, and maintenance value. Not for test implementation or a single delivery review.
ln-21-documentation-auditor
Audits documentation and comments for trustworthy claims, coverage, and discoverability. Not for code, test, or architecture audits.
ln-22-codebase-auditor
Audits cross-cutting code health, security, delivery, and maintainability when no specialist audit is primary. Not for a single delivery review.
ln-24-architecture-auditor
Audits implemented architecture, boundaries, dependencies, and configuration ownership. Not for documenting current state or reviewing plans.