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 alonf/specrew --skill iteration-governance-readiness-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/iteration-governance-readiness-review)<a href="https://agentmods.dev/skills/alonf/specrew/iteration-governance-readiness-review"><img src="https://agentmods.dev/badge/skills/alonf/specrew/iteration-governance-readiness-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/alonf/specrew/iteration-governance-readiness-review"><img src="https://agentmods.dev/badge/skills/alonf/specrew/iteration-governance-readiness-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00026 | $0.00814 |
| Opus 5 | $0.00013 | $0.00407 |
| Sonnet 5 | $0.00005 | $0.00163 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
iteration-governance-readiness-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 8d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
Use this when reviewer findings claim an iteration is fixed or execution-ready and you need to verify the live repo state rather than trusting the narrative.
Patterns
- Read the contract and the live artifact first; treat decision memos as supporting context, not proof.
- Run the validator and separate gate-health questions from artifact-quality questions.
- Accept a validator fix when it stops crashing and surfaces real contract failures.
- Reject execution readiness when the plan or other required artifacts still fail the live validator.
- If rejecting, name the next revision owner for each rejected artifact and respect author lockout rules.
- On re-review, check each previously cited defect directly in the live file and require the validator to clear the same artifact before flipping from NEEDS-WORK to PASS.
- Keep artifact readiness separate from broader coordination prerequisites; only fail the gate on approvals or consensus items when they are part of the governing requirement or prior rejection basis.
- When the prior rejection was "missing iteration boundary + capacity mismatch," require the repaired feature
plan.mdandtasks.mdto show an explicit multi-iteration split that stays within.specrew/iteration-config.ymlcapacity before you even inspect the target iteration artifacts. - After that package-level check, validate the specific repaired slice with
validate-governance.ps1 -IterationPath <iteration>and treat a clean pass plus synchronizedplan.md/state.md/drift-log.mdas evidence that the only remaining blocker is explicit human execution approval, not another planning defect. - For review/demo transitions, do not stop at passing regression tests: compare
state.mdagainst the live task table inplan.md, then exercise the reviewer-packet scaffold path because missing phase metadata or helper crashes can leave review artifacts non-binding even when tests stay green. - After
review.mdexists, immediately re-check lifecycle truth:plan.mdcan no longer stayexecuting, andstate.mdcan no longer describe review as deferred or pending. The validator treatsreview.mdas active phase evidence and will reject stale execution-era narratives. - If reviewer-owned quality gates stay
plannedafter a scaffold rerun, inspect the iteration plan'sRequired Quality Gatestable forCategorymetadata (mechanical,tooling,manual-evidence); without it, the scaffold cannot promote those gates to review-complete evidence.
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.
- 8d ago First seen · 49 lines · 26 tokens per session scan A 69ebde48666c
iteration-governance-readiness-review is a skill published in the GitHub repository alonf/specrew (54 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 814 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.