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/ddunnock/claude-plugins/docs.initgit clone --depth 1 https://github.com/ddunnock/claude-pluginsWhat 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.00000 | $0.00264 |
| Opus 5 | $0.00000 | $0.00132 |
| Sonnet 5 | $0.00000 | $0.00053 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
docs.init 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 2d 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
Establish documentation foundation for this project.
Before Starting
Read and internalize the behavioral constraints in GUARDRAILS.md.
Workflow
- Check existing state (docs/, .claude/memory/docs-*.md)
- Detect project type (library, CLI, app, service)
- Create docs/ structure with Diátaxis layout
- Create documentation memory files
- Present summary and next steps
Outputs to Create
docs/
├── index.md
├── user/
│ ├── getting-started/
│ ├── guides/
│ ├── concepts/
│ └── reference/
├── developer/
│ ├── architecture/
│ ├── contributing/
│ └── reference/api/
└── _meta/
├── inventory.md
├── plan.md
└── progress.md
.claude/memory/
├── docs-constitution.md
├── docs-terminology.md
└── docs-sources.md
Guardrails
- No assumptions without approval
- No proceeding without confirmation
- Idempotent: skips existing, updates changed, preserves customizations
After completion, suggest /docs.inventory as next step.
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.
- 2d ago First seen · 43 lines · 0 tokens per session scan A 09668dc88a99
docs.init is a command published in the GitHub repository ddunnock/claude-plugins (12 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 264 tokens. 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
learn
Force claude-smart to extract learnings from this session now.
component
Scaffold a new React component grounded in the paper-mono primitives. Requires explicit kind or a nearest-existing-component match. No empty divs, no speculative scaffolding.
memory-store
Store an insight, decision, or pattern to memory.
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
no-vibe
Enter no-vibe mode in OpenCode (tutor mode, no direct project file writes).
teach-me-testing
Teach testing progressively through structured sessions. Use when user says ""lets learn testing"" or ""I want to study test practices"".