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/taylorleese/claude-toolzWrote 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/taylorleese/claude-toolz/improve-all-docs)<a href="https://agentmods.dev/commands/taylorleese/claude-toolz/improve-all-docs"><img src="https://agentmods.dev/badge/commands/taylorleese/claude-toolz/improve-all-docs.svg" alt="Measured on agentmods" 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.00021 | $0.00285 |
| Opus 5 | $0.00010 | $0.00143 |
| Sonnet 5 | $0.00004 | $0.00057 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
improve-all-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 7d 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
Run a static quality audit of the project's documentation — independent of the current session's work. Unlike /revise-all-docs (which captures
learnings from this session), this command scores each doc file against type-appropriate rubrics and proposes targeted fixes.
Invoke the revise-all-docs:all-docs-improver skill via the Skill tool. It owns the full workflow:
- Discovery — find every
CLAUDE.md,README.md, anddocs/**/*.mdin the repo. - Quality Assessment — score each file against criteria appropriate to its type (delegates
CLAUDE.mdaudits to theclaude-md-management:claude-md-improverskill). - Quality Report — print a unified per-file score table with specific issues.
- Targeted Updates — propose concrete diffs, one concept per line, no filler.
- Apply — only after explicit user approval; use
Edit(neverWrite).
After the skill returns, summarize: which files changed, how many lines added/removed per file, and any learnings the user declined.
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.
- 7d ago First seen · 18 lines · 21 tokens per session scan A 9661c0132f24
improve-all-docs is a command published in the GitHub repository taylorleese/claude-toolz (3 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 285 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.