Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add racecraft-lab/racecraft-plugins-public/plugin install speckit-proWrote 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/racecraft-lab/racecraft-plugins-public/speckit-plan-review)<a href="https://agentmods.dev/skills/racecraft-lab/racecraft-plugins-public/speckit-plan-review"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/speckit-plan-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/racecraft-lab/racecraft-plugins-public/speckit-plan-review"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/speckit-plan-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.00000 | $0.02301 |
| Opus 5.5 | $0.00000 | $0.00920 |
| Sonnet 5.5 | $0.00000 | $0.00460 |
| Haiku 4.5 | $0.00000 | $0.00230 |
Grade A, and why
speckit-plan-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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpecKit Plan Review
An interview between planning and implement. The user decides what to fix. You guide the interview and call runner helpers. The runner owns every rule about revisions and findings.
This skill builds a repair prompt, or an implement prompt, for the user to copy. It sends nothing and
starts no planning, repair or implementation. It records an approval only after the user explicitly
approves the final revision with every finding fixed and checked (step 5). Its writes are the user's
active requests, which the runner records in the feature's planning-findings.json, and that one approval.
Capability discovery & grounding
Before recommending, enumerate the tools and skills your session actually exposes — do not assume a fixed set; the user may have installed anything — and select the best fit per ${CLAUDE_PLUGIN_ROOT}/skills/speckit-autopilot/references/capability-discovery.md. Ground every external fact you assert in a real tool, skill, or file result per ${CLAUDE_PLUGIN_ROOT}/skills/speckit-autopilot/references/grounding.md, and abstain when nothing grounds it.
Before recommending, enumerate the tools and skills your session actually exposes — do not assume a fixed set; the user may have installed anything — and select the best fit per ../speckit-autopilot/references/capability-discovery.md. Ground every external fact you assert in a real tool, skill, or file result per ../speckit-autopilot/references/grounding.md, and abstain when nothing grounds it.
Installed Runtime Contract
Resolve <plugin-root> per Installed runner transport.
Send one JSON request per runner call on stdin and read one JSON reply. Add no shell step. Runner helpers follow the session's permissions; if one is denied, say so and stop that step.
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.
- yesterday Changed · +35 lines e1f3c53faa09
- 2d ago First seen · 125 lines · 0 tokens per session scan A fe027980d10e
speckit-plan-review is a skill published in the GitHub repository racecraft-lab/racecraft-plugins-public (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,301 tokens. 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-19.
Other skills, from other repositories
build-executor
Execute an active direct request or approved planned change. Native continuous implementation is the default; existing legacy changes retain their recorded contract obligations.
bug-investigator
Use when encountering any bug, test failure, or unexpected behavior during spec-superflow execution, before proposing fixes. Invoked automatically when build-executor hits a blockage.
spec-writer
Create or refine spec-superflow planning artifacts. Invoke when the change is understood well enough to write proposal.md, specs/, design.md, and tasks.md.
contract-builder
Maintain an execution contract only for an existing legacy change that requires one. New direct/planned changes do not invoke this skill when a contract is absent.
codex-issue-coordinator
Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.
need-explorer
Clarify intent, scope, constraints, and success criteria before artifact creation. Invoke when the request is fuzzy, the user is comparing options, or the workflow needs a stable change definition before writing artifacts.