Borrowing it
Nothing to install: this file belongs to anthony-spruyt/claude-plugins. 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/anthony-spruyt/claude-plugins/main/.claude/skills/spec-review/SKILL.mdgit clone --depth 1 https://github.com/anthony-spruyt/claude-pluginsWrote 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/anthony-spruyt/claude-plugins/spec-review)<a href="https://agentmods.dev/skills/anthony-spruyt/claude-plugins/spec-review"><img src="https://agentmods.dev/badge/skills/anthony-spruyt/claude-plugins/spec-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/anthony-spruyt/claude-plugins/spec-review"><img src="https://agentmods.dev/badge/skills/anthony-spruyt/claude-plugins/spec-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.00059 | $0.00374 |
| Opus 5.5 | $0.00024 | $0.00150 |
| Sonnet 5.5 | $0.00012 | $0.00075 |
| Haiku 4.5 | $0.00006 | $0.00037 |
Grade A, and why
spec-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 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.
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
Spec Review
You are reviewing the spec at $spec.
Instructions
- Read the review brief at review-brief.md
- Read the full spec at
$spec - Spawn a general-purpose subagent to perform the review. Brief it with:
- The full review brief contents
- The spec file path to review
- Instruction to use Context7 for library/framework validation
- Instruction to verify the spec's claims against the code and config in the repo, and against live systems where the repo alone is insufficient
- The contents of
.claude/spec-review.mdin the repo, if it exists: where and how to verify claims in this repo - Instruction to cross-reference findings against the spec's own risks table, phase checklists, and tradeoff callouts before flagging — do not raise concerns the spec already addresses
- After receiving findings, present results organized by severity
- Offer to update the spec based on findings
Rules
- Findings go in the conversation, not the spec. Don't append review notes, summaries, or review round logs to the spec file: it is the design document, not a review journal.
- Only edit the spec to fix actual issues identified in findings (incorrect claims, missing sections, design gaps). Each edit should improve the spec's content, not add meta-commentary about the review process.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 33 lines · 59 tokens per session scan A cfc8659f3ced
spec-review is a skill published in the GitHub repository anthony-spruyt/claude-plugins (2 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 374 once invoked, about $0.0002 per session on Opus 5.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-10-16.
Other skills, from other repositories
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…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…