Borrowing it
Nothing to install: this file belongs to MikahNiehaus/ClaudeBoost. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MikahNiehaus/ClaudeBoost/main/.claude/commands/boost.mdgit clone --depth 1 https://github.com/MikahNiehaus/ClaudeBoostWrote 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/mikahniehaus/claudeboost/boost)<a href="https://agentmods.dev/commands/mikahniehaus/claudeboost/boost"><img src="https://agentmods.dev/badge/commands/mikahniehaus/claudeboost/boost/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/mikahniehaus/claudeboost/boost"><img src="https://agentmods.dev/badge/commands/mikahniehaus/claudeboost/boost.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.00032 | $0.02999 |
| Opus 5.5 | $0.00013 | $0.01200 |
| Sonnet 5.5 | $0.00006 | $0.00600 |
| Haiku 4.5 | $0.00003 | $0.00300 |
Grade C, and why
boost scanned grade C with 3 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 8d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -s -X POST http://127.0.0.1:8613/index-project -H "Content-Type: application/json" -d "{\"project_path\": \"${CLAUDEBOOST_HOME}\", \"force\": true}" Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
**statusLine** — read `~/.claude/settings.json` with the Read tool; check whether Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
If installed: `curl -s --max-time 3 http://localhost:11434/` (running or not). The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 8d ago First seen · 302 lines · 32 tokens per session scan C de5032de81fa
boost is a command published in the GitHub repository MikahNiehaus/ClaudeBoost (9 stars, last pushed yesterday), with no licence file. It adds 32 tokens to every session and 2,999 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 3 findings (sends data to an external url, reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-02.
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.