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 skills add MicSm/boffin --skill boffin-reviewgit clone --depth 1 https://github.com/MicSm/boffinWrote 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/micsm/boffin/boffin-review)<a href="https://agentmods.dev/skills/micsm/boffin/boffin-review"><img src="https://agentmods.dev/badge/skills/micsm/boffin/boffin-review/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/skills/micsm/boffin/boffin-review"><img src="https://agentmods.dev/badge/skills/micsm/boffin/boffin-review.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.00053 | $0.00251 |
| Opus 5 | $0.00026 | $0.00125 |
| Sonnet 5 | $0.00011 | $0.00050 |
| Haiku 4.5 | $0.00005 | $0.00025 |
Grade A, and why
boffin-review 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 12d 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
Boffin Review
Read AGENTS.md at the installed plugin root, two directories above this file. It is authoritative; this skill only activates its review path.
Preserve the user's request mode: a review or audit does not authorize edits. Scope the review to the requested files or changes, route through the relevant pack leaves (the packs/ tree ships beside that AGENTS.md at the plugin root), and walk stages S00-S06 in order with EXCLUDES first.
For open-ended review, cleanup, or refactoring work, complete the contract's read-only first pass and findings ledger before proposing or applying fixes. If the user also requests implementation, drain that ledger one finding at a time with the narrowest proving check.
Use the active lite, full, or max profile only to vary ambition and cleanup pressure. Never use it to lower the correctness or safety floor.
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.
- 12d ago First seen · 16 lines · 53 tokens per session scan A 4d8e14f8a8f1
boffin-review is a skill published in the GitHub repository MicSm/boffin (38 stars, last pushed 20d ago), licensed MIT. It adds 53 tokens to every session and 251 once invoked, about $0.0003 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-30.
Other skills, from other repositories
claude-c-suite-audit
Use when auditing or release-checking the Claude C-Suite plugin's own command conformance.
claude-c-suite-cto
Use for architecture, tech debt, refactoring, dependency, scaling, migration, and codebase health reviews.
claude-c-suite-dx-lead
Use for developer experience, API ergonomics, SDK usability, docs quality, onboarding, and error-message reviews.
code-quality-principles
Applies KISS, YAGNI, and SOLID principles for clean code with reduced complexity. Use when refactoring or reviewing code for over-engineering.
plugin-review
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.
vue-best-practices
A review checklist for Vue 2 and Vue 3 components, covering component names, prop declarations, TypeScript casts, API styles and complex template expressions.