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/alonf/specrew/specrew-reviewnpx skills add alonf/specrew --skill specrew-reviewgit clone --depth 1 https://github.com/alonf/specrewWrote 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/alonf/specrew/specrew-review)<a href="https://agentmods.dev/skills/alonf/specrew/specrew-review"><img src="https://agentmods.dev/badge/skills/alonf/specrew/specrew-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.1 | $0.00018 | $0.01548 |
| Opus 5 | $0.00009 | $0.00774 |
| Sonnet 5 | $0.00004 | $0.00310 |
| Haiku 4.5 | $0.00002 | $0.00155 |
Grade A, and why
specrew-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 6d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
specrew-review
Type: Operational Skill
Schema: v1
Status: Active
Namespace: /specrew
Canonical command: /specrew-review
Purpose
Trigger or inspect the Specrew review-oriented workflow. Use live mode to run the continuous co-review runtime and persist reviewer evidence under .specrew/review/inline/<run-id>/; use replay mode to inspect an existing reviewer closeout packet for a completed iteration.
When to Use
- When a reviewer needs a live continuous co-review run before or during a review boundary.
- When a reviewer wants to inspect the review summary for a completed iteration.
- When replaying the reviewer closeout packet.
- Invoke this skill when the user says: "Run the reviewer", "Run live review", "Show the review summary", "Review the iteration", "Show reviewer output".
Boundary Safety
This skill supports review work but does not bypass the required human decision point. A human reviewer must still explicitly approve lifecycle advancement. Invoking /specrew-review is not equivalent to approving an iteration for closure or advancement.
Feature 016 rule: Humans remain the approval authority for major boundary transitions. This command may not imply authorization to advance from any lifecycle boundary.
Coexistence Contract
This skill is part of the /specrew-* command surface. It coexists with /speckit.* review-related commands without collision or shadow. Using /specrew-review does not substitute for /speckit.* lifecycle actions that require explicit human authorization.
Invocation
/specrew-review [<iteration>] [--project-path <path>] [--feature <id>]
[--iteration <NNN>] [--quiet] [--json] [--open]
/specrew-review --live [--baseline-ref <git-ref>] [--project-path <path>] # baseline auto-anchors for signoff; an explicit --baseline-ref run is exploratory-only
[--checkpoint-id <id>] [--run-id <id>] [--host <host>]
[--model <model>] [--effort <effort>] [--authorization-ref <ref>]
[--code-writer-host <host>]
[--design-context-ref <path>] [--allowed-path <path>]
[--forbidden-path <path>] [--exclude-path <path>]
[--reviewer-config <path>] [--schema-root <path>]
[--run-root <path>] [--timeout-seconds <N>]
[--fallback-policy <none|one-authorized-availability-fallback>]
[--preserve-debug]
/specrew-review --reconcile-run <run-id> [--project-path <path>]
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.
- 6d ago First seen · 111 lines · 18 tokens per session scan A 40223da4f304
specrew-review is a skill published in the GitHub repository alonf/specrew (54 stars, last pushed 4d ago), licensed MIT. It adds 18 tokens to every session and 1,548 once invoked, about $0.0001 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
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…