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/claude-code-community-ireland/claude-code-resources/documentgit clone --depth 1 https://github.com/Claude-Code-Community-Ireland/claude-code-resourcesWhat 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.00330 |
| Opus 5 | $0.00005 | $0.00165 |
| Sonnet 5 | $0.00002 | $0.00066 |
| Haiku 4.5 | $0.00001 | $0.00033 |
Grade A, and why
document 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
Document Workflow
You are generating documentation for a codebase, module, or API.
Steps
-
Determine the target: Read
$ARGUMENTSto understand what needs documenting.- If a file path: Document that specific file or module
- If "readme" or "project": Generate a project README
- If "api": Generate API documentation
- If "changelog": Generate a changelog entry
- If "runbook": Generate an operational runbook
- If empty: Ask the user what to document
-
Read the code thoroughly: Before writing any documentation, read all relevant source files. Understand what the code does, its public API, configuration options, and edge cases.
-
Launch the doc-writer: Use the Task tool to spawn the
doc-writeragent with:Generate documentation for: Target: $ARGUMENTS Type: [detected doc type] Code context: [summary of what the code does]
Follow documentation standards. Use active voice, concrete examples, and progressive disclosure. Include code examples where relevant.
-
Write the output: Create or update the documentation file in the appropriate location.
-
Verify: Confirm all code examples in the documentation are accurate and all links resolve.
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 · 35 lines · 10 tokens per session scan A cf14fba3cbdc
document is a command published in the GitHub repository Claude-Code-Community-Ireland/claude-code-resources (10 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 330 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.