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/lukedj78/dev-flow/spec-reviewnpx skills add lukedj78/dev-flow --skill spec-reviewgit clone --depth 1 https://github.com/lukedj78/dev-flowWrote 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/lukedj78/dev-flow/spec-review)<a href="https://agentmods.dev/skills/lukedj78/dev-flow/spec-review"><img src="https://agentmods.dev/badge/skills/lukedj78/dev-flow/spec-review.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.00211 | $0.02931 |
| Opus 5 | $0.00105 | $0.01465 |
| Sonnet 5 | $0.00042 | $0.00586 |
| Haiku 4.5 | $0.00021 | $0.00293 |
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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
spec-review — did we build what the PRD asked, the way the contract says?
Two-axis review of the diff between HEAD and a fixed point:
- Spec — does the change faithfully implement what
.workflow/PRD.md/tasks.mdasked for? - Standards — does it obey the contract this project was built under?
Both run as parallel sub-agents so neither pollutes the other's context, then this skill reports them side by side.
Credit. The two-axis structure, the parallel-sub-agent split, the refusal to merge verdicts and the Fowler smell baseline are adapted from Matt Pocock's
code-reviewskill (mattpocock/skills, MIT — the skill now lives atdocs/engineering/code-review.md; both paths checked 2026-08-26) and the essay behind it. What's ours is the half his skill has to search for: in a dev-flow project the spec and the standards are at known paths.
Why this is not /code-review
Claude Code ships a built-in /code-review, and Pocock's own write-up lists the name collision as a
known problem. This skill is deliberately not that, in name or in remit:
Built-in /code-review |
spec-review |
|
|---|---|---|
| Reviews | the code, generically | the code against this project's spec and contract |
| Knows | the diff | .workflow/PRD.md, tasks.md, meta.json#stack, #artifacts, #history |
| Answers | "is this good code?" | "is this the thing we said we'd build, built our way?" |
Run both if you like — they don't overlap. Without a .workflow/, this skill refuses and points
at the built-in: with no spec and no declared stack, both of its axes are guesswork.
Workflow
1. Pin the fixed point — and fail here, not inside a sub-agent
Whatever the user names is the fixed point (a SHA, main, a tag, HEAD~5). If they didn't say, ask.
git rev-parse <fixed-point> # must resolve
git diff <fixed-point>...HEAD --stat # three-dot: compare against the merge-base
git log <fixed-point>..HEAD --oneline # the commits under review
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.
- 4d ago First seen · 175 lines · 211 tokens per session scan A c15dd3b051b0
spec-review is a skill published in the GitHub repository lukedj78/dev-flow (6 stars, last pushed yesterday), licensed MIT. It adds 211 tokens to every session and 2,931 once invoked, about $0.0011 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-31.
Other skills, from other repositories
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
agui-dotnet-streaming-chat
Get started with the AG-UI .NET SDK: bootstrap and run your first streaming-chat app (client + server) with the AG-UI .NET NuGet packages (AGUI.Client, AGUI.Server, AGUI.Formatting, AGUI.Abstractions). USE FOR: which packages to install and how to wire them; constructing an AGUIChatClient against an endpoint and…
agui-dotnet-sample-step
Add a GettingStarted sample Step (a Server/Client pair) to the AG-UI .NET SDK that demonstrates one protocol feature the way we want users to write it. USE FOR: adding a new samples/GettingStarted/StepNN Server+Client pair, wiring it into AGUI.slnx and the integration-test project, giving it a deterministic…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
taiyi-ui-design
TaiyiForge 第 4 阶段 — UI/UX 契约，产出 UI-DESIGN.md。四端通用。.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…