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 skills/ridges0315/claude-boost/boostnpx skills add ridges0315/claude-boost --skill boostgit clone --depth 1 https://github.com/ridges0315/claude-boostWrote 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/skills/ridges0315/claude-boost/boost)<a href="https://agentmods.dev/skills/ridges0315/claude-boost/boost"><img src="https://agentmods.dev/badge/skills/ridges0315/claude-boost/boost.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 | $0.00047 | $0.02067 |
| Opus 5 | $0.00023 | $0.01033 |
| Sonnet 5 | $0.00009 | $0.00413 |
| Haiku 4.5 | $0.00005 | $0.00207 |
Grade B, and why
boost scanned grade B with 1 finding 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 3d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
2. **settings.json** — `~/.claude/settings.json` has permissions with at least one allow entry? How it starts
The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Boost — Diagnose and Optimize Your Claude Code Setup
Diagnose the user's Claude Code configuration, display their Boost Score, and actively help them set up missing items.
Instructions
Phase 1: Diagnose
Run the exact same diagnostic checks as the boost-check skill. Check all 9 items across 3 levels:
Level 1 — Essentials (3 items)
- CLAUDE.md — exists in project root? Has > 5 lines? Has model routing section?
- settings.json —
~/.claude/settings.jsonhas permissions with at least one allow entry? - Memory system — project memory directory has MEMORY.md with entries?
Level 2 — Power Features (4 items)
4. CLAUDE.md advanced — has context management / workflow mode sections (2+ keywords)?
5. MCP servers — ~/.claude/mcp.json or .mcp.json has at least one server?
6. Plugins — installed_plugins.json has 2+ plugins (excluding boost)?
7. Git integration — current directory is a git repo?
Level 3 — Expert (2 items)
8. Hooks — settings.json has custom hooks?
9. Keybindings — ~/.claude/keybindings.json exists with custom bindings?
Phase 2: Display Score
Show the Boost Score:
╔══════════════════════════════════════════════════╗
║ Boost Score: X/9 ║
║ Level 1: a/3 | Level 2: b/4 | Level 3: c/2 ║
╚══════════════════════════════════════════════════╝
Then list all items with ✓/✗ status.
Phase 3: Guide and Act
Start from the lowest level with missing items. For each missing item, offer to set it up.
If the user passed a level argument (e.g., /boost 2), skip to that level.
Setting Up: CLAUDE.md (Level 1)
When CLAUDE.md is missing or sparse:
- Auto-detect project context:
- Read
package.json→ extract name, description, dependencies, scripts - Read
requirements.txtorpyproject.toml→ extract Python dependencies - Read
go.mod→ extract Go module info - Read
Cargo.toml→ extract Rust crate info - Read
.eslintrc*,.prettierrc*,.editorconfig→ extract code style rules - Read
jest.config*,vitest.config*,pytest.ini,tsconfig.json→ extract test config - Read
.gitignore→ infer restricted files - Read
README.mdfirst 20 lines → extract project description - If none of these exist, note "No project config files detected"
- Read
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.
- 3d ago First seen · 233 lines · 47 tokens per session scan B 4b376d975059
boost is a skill published in the GitHub repository ridges0315/claude-boost (2 stars, last pushed 5mo ago), licensed MIT. It adds 47 tokens to every session and 2,067 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…