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/boost-checknpx skills add ridges0315/claude-boost --skill boost-checkgit 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-check)<a href="https://agentmods.dev/skills/ridges0315/claude-boost/boost-check"><img src="https://agentmods.dev/badge/skills/ridges0315/claude-boost/boost-check.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.00031 | $0.01135 |
| Opus 5 | $0.00015 | $0.00567 |
| Sonnet 5 | $0.00006 | $0.00227 |
| Haiku 4.5 | $0.00003 | $0.00113 |
Grade B, and why
boost-check 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 5d 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.
- Check: Read `~/.claude/settings.json` How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Boost Check — Configuration Diagnostic
Run a read-only diagnostic of the user's Claude Code setup. Report findings without making changes.
Instructions
When this skill is invoked, perform ALL diagnostic checks below, then display the results.
If the user passes an argument (e.g., /boost-check 2), only diagnose that level. Otherwise diagnose all levels.
Step 1: Run Diagnostics
Check each item below. For each, record status as CONFIGURED or MISSING.
Level 1 — Essentials
1.1 CLAUDE.md
- Check: Does
CLAUDE.mdexist in the current project root? - How: Use Glob to find
CLAUDE.mdin the working directory - CONFIGURED if: File exists AND has more than 5 lines
- MISSING if: File does not exist or has 5 or fewer lines
- Also check: Does it contain a "Model routing" or "model" section? If CLAUDE.md exists but has no model routing → flag as "CLAUDE.md exists but missing model routing"
1.2 settings.json
- Check: Read
~/.claude/settings.json - CONFIGURED if: File exists AND has a
permissionsobject with at least oneallowentry - MISSING if: File doesn't exist, or permissions is empty, or all entries are deny/empty
1.3 Memory System
- Check: Does the project's memory directory have a
MEMORY.md? - How: Read
~/.claude/projects/— find the subdirectory matching the current project path, then check forMEMORY.md - CONFIGURED if: MEMORY.md exists and has at least one entry
- MISSING if: No MEMORY.md or empty
Level 2 — Power Features
2.1 CLAUDE.md Advanced
- Check: Does CLAUDE.md contain sections for context management or workflow modes?
- How: Read CLAUDE.md, search for keywords: "compact", "context management", "mode", "workflow", "debug", "routing"
- CONFIGURED if: At least 2 of these keywords found in distinct sections
- MISSING if: Fewer than 2 found
2.2 MCP Servers
- Check: Read
~/.claude/mcp.jsonand project.mcp.json - CONFIGURED if: At least one MCP server is defined in either file
- MISSING if: Neither file exists or both are empty
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.
- 5d ago First seen · 121 lines · 31 tokens per session scan B 828fc010377e
boost-check is a skill published in the GitHub repository ridges0315/claude-boost (2 stars, last pushed 5mo ago), licensed MIT. It adds 31 tokens to every session and 1,135 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…