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/infopibe/everything-claude-code/update-docsgit clone --depth 1 https://github.com/Infopibe/everything-claude-codeWhat 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.00005 | $0.00309 |
| Opus 5 | $0.00003 | $0.00154 |
| Sonnet 5 | $0.00001 | $0.00062 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
update-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 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.
This is a copy
100% identical to update-docs — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Update Docs Command
Update documentation to reflect recent changes: $ARGUMENTS
Your Task
- Identify changed code -
git diff --name-only - Find related docs - README, API docs, guides
- Update documentation - Keep in sync with code
- Verify accuracy - Docs match implementation
Documentation Types
README.md
- Installation instructions
- Quick start guide
- Feature overview
- Configuration options
API Documentation
- Endpoint descriptions
- Request/response formats
- Authentication details
- Error codes
Code Comments
- JSDoc for public APIs
- Complex logic explanations
- TODO/FIXME cleanup
Guides
- How-to tutorials
- Architecture decisions (ADRs)
- Troubleshooting guides
Update Checklist
- README reflects current features
- API docs match endpoints
- JSDoc updated for changed functions
- Examples are working
- Links are valid
- Version numbers updated
Documentation Quality
Good Documentation
- Accurate and up-to-date
- Clear and concise
- Has working examples
- Covers edge cases
Avoid
- Outdated information
- Missing parameters
- Broken examples
- Ambiguous language
IMPORTANT: Documentation should be updated alongside code changes, not as an afterthought.
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 · 68 lines · 5 tokens per session scan A 2a036d2ed5b6
update-docs is a command published in the GitHub repository Infopibe/everything-claude-code (8 stars, last pushed 5mo ago), licensed MIT. It adds 5 tokens to every session and 309 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to update-docs, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.