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/stefan-jansen/claude-code-toolkitWrote 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/stefan-jansen/claude-code-toolkit/docs)<a href="https://agentmods.dev/commands/stefan-jansen/claude-code-toolkit/docs"><img src="https://agentmods.dev/badge/commands/stefan-jansen/claude-code-toolkit/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/stefan-jansen/claude-code-toolkit/docs"><img src="https://agentmods.dev/badge/commands/stefan-jansen/claude-code-toolkit/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.00014 | $0.00462 |
| Opus 5.5 | $0.00006 | $0.00185 |
| Sonnet 5.5 | $0.00003 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
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
Documentation Operations
Input: $ARGUMENTS
Usage
/docs fetch # Fetch official Claude Code & library docs
/docs fetch --force # Force complete re-fetch
/docs fetch --libraries # Focus on project dependency docs
/docs search "command syntax" # Search all cached documentation
/docs generate "Added auth" # Generate/update docs after changes
/docs generate --api # Focus on API documentation
Process
1. Determine Operation
- fetch: Download external documentation to
.claude/docs/ - search: Query cached documentation and library docs
- generate: Create/update project documentation
- No args: Show usage guidance
2. Fetch Operations
- Identify documentation sources (official + dependencies)
- Create/update cache in
.claude/docs/ - Track versions and timestamps
- Create searchable index
With Context7: Auto-detect dependencies → resolve library IDs → fetch version-matched docs
3. Search Operations
- Index search for fast results
- Full-text search across cache
- Rank by relevance
With Context7: Resolve library names → fetch live documentation → return focused results
4. Generate Operations
- Assess existing documentation
- Identify gaps and outdated content
- Generate API docs, README updates, migration guides
- Test code examples
Cache Structure
.claude/docs/
├── official/ # Claude Code documentation
├── libraries/ # Third-party library docs
├── project/ # Project-specific docs
└── cache_metadata.json
MCP Enhancement
Context7 (when available):
resolve-library-id→ find library documentationget-library-docs→ fetch comprehensive docs- Fallback: WebFetch with manual caching
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 · 66 lines · 14 tokens per session scan A 8101ee3e45b3
docs is a command published in the GitHub repository stefan-jansen/claude-code-toolkit (90 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 462 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-08-30.
Other commands, from other repositories
workflow-classify
Classify task size (S/M/L/XL) and recommend the appropriate workflow pipeline.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
sonarqube
Analyze SonarCloud quality issues for a specific PR.
plan-start
5-phase planning command: PRD analysis, design review, technical decisions, dynamic research team, metrics. Produces a complete implementation plan + ADRs before any code is written.
refactor
Analyze code for SOLID violations and suggest targeted improvements.