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/travisjneuman/.claudeWrote 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/travisjneuman/.claude/update-docs)<a href="https://agentmods.dev/commands/travisjneuman/.claude/update-docs"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/update-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/travisjneuman/.claude/update-docs"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/update-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.00009 | $0.00239 |
| Opus 5.5 | $0.00004 | $0.00096 |
| Sonnet 5.5 | $0.00002 | $0.00048 |
| Haiku 4.5 | $0.00001 | $0.00024 |
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 24d 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
Update Documentation
Scan for recently modified files and update corresponding documentation.
Instructions
- Check which files were modified in this session using
git diff --name-onlyandgit diff --cached --name-only - For each modified area, update the corresponding docs:
| Modified Area | Update |
|---|---|
skills/ |
Regenerate skills/MASTER_INDEX.md — run bash ~/.claude/scripts/regenerate-index.sh |
commands/ |
Verify command appears in skill listings |
agents/ |
Update agents/README.md |
hooks/ or settings.json |
Update docs/reference/tooling/ docs as needed |
CLAUDE.md |
Verify satellite files are consistent |
plugins/ |
Update docs/MARKETPLACE-GUIDE.md if plugin list changed |
- Update
cache/changelog.mdwith a summary of changes made - Commit documentation updates together with the changes they describe
If arguments provided, focus on: $ARGUMENTS
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.
- 24d ago Changed · +3 lines · +9 tokens per session 91c822937330
- 1mo ago First seen · 23 lines · 0 tokens per session scan A ab9085e89ed9
update-docs is a command published in the GitHub repository travisjneuman/.claude (105 stars, last pushed 2d ago), licensed MIT. It adds 9 tokens to every session and 239 once invoked, about $0.0000 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-09-03.
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.
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.
speckit.bug.test
Validate that a previously fixed bug is resolved and record the verification report.