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 prime-radiant-inc/iterative-development --skill running-an-iterationgit clone --depth 1 https://github.com/prime-radiant-inc/iterative-developmentWrote 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/prime-radiant-inc/iterative-development/running-an-iteration)<a href="https://agentmods.dev/skills/prime-radiant-inc/iterative-development/running-an-iteration"><img src="https://agentmods.dev/badge/skills/prime-radiant-inc/iterative-development/running-an-iteration/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/prime-radiant-inc/iterative-development/running-an-iteration"><img src="https://agentmods.dev/badge/skills/prime-radiant-inc/iterative-development/running-an-iteration.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.00051 | $0.01645 |
| Opus 5 | $0.00026 | $0.00822 |
| Sonnet 5 | $0.00010 | $0.00329 |
| Haiku 4.5 | $0.00005 | $0.00164 |
Grade A, and why
running-an-iteration 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 10d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Running an Iteration
Overview
Drives one iteration: picks the next pending, runs sentinel corpus baseline, runs pre-iteration scope review via PAR, decomposes into code and evidence tasks, dispatches implementing-tasks, runs impacted + sentinel scenarios at wrap-up, and updates the roadmap and iteration log.
When to Use
Invoked by iterative-development inside the main loop. Each invocation runs exactly one iteration. After return, the orchestrator invokes auditing-progress.
Script Location
All scripts referenced below live in this skill's scripts/ directory, next to this SKILL.md file.
Iteration Process
1. Pick next iteration
Read docs/superpowers/iterations/roadmap.md, find the first iteration with status pending.
2. Load scope context
Read the per-epic files in docs/superpowers/iterations/requirements/ to load the full story cards for each committed story ID. Only read the epic files that contain stories for this iteration — not all of them. Also:
- Load the next 3 pending iterations from the roadmap for look-ahead
- Read
docs/superpowers/iterations/behavior-scenarios.mdto identify impacted scenarios - Read
docs/superpowers/iterations/behavior-corpus.mdto identify sentinel scenarios
3. Run sentinel corpus baseline
Before any code changes, run every scenario in the behavior corpus with run cadence sentinel:
- If all sentinels pass: record baseline as clean, proceed
- If any sentinel fails: the failure predates this iteration. Record it, create a gap story for it, but proceed with the iteration (the gap will be addressed in a follow-up)
This establishes whether regressions exist before the current iteration starts.
4. Pre-iteration consistency audit
Before planning any work, verify that artifact state is consistent:
- Citation check:
python3 "scripts/check_citations.py" docs/superpowers/iterations/roadmap.md docs/superpowers/iterations/requirements/— if citations fail, stop and fix the roadmap. - Status reconciliation: For each story in this iteration's scope, verify:
- Stories listed in the roadmap iteration are not already marked
done:ITER-XXXXin the requirements index (unless code/tests actually exist for them) - Stories marked
donein the requirements index actually have corresponding code and tests - No story appears in multiple pending iterations
- Stories listed in the roadmap iteration are not already marked
- Epic counter validation: Spot-check that epic progress counters match the actual count of
donestories.
What ships with it
3 files 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.
- 10d ago First seen · 137 lines · 51 tokens per session scan A 330359478d65
running-an-iteration is a skill published in the GitHub repository prime-radiant-inc/iterative-development (179 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 51 tokens to every session and 1,645 once invoked, about $0.0003 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
design
Create a doc-as-code design package from a PRD or SPEC. Conditionally generates C4 diagrams (Context/Container/Component), sequence diagrams, ER diagram + Data Dictionary, OpenAPI 3.0, AsyncAPI 3.0, ADRs, domain glossary, state diagrams, and deployment view as Mermaid-rendered Markdown files. Use when PM mentions…
review-pr
A pull-request review skill for evaluating proposed code changes and posting a quality verdict. A pull request is a request to merge changes into a shared codebase.
tasks
A task-breakdown tool that turns a plan, specification, feature brief, bug report, technical-debt item, or chore into small TASK-NNN work items. Technical debt means postponed cleanup or design work in a codebase.
continue
Autonomous work — find and execute ready tasks.
reconcile-docs
Best-effort reconciliation of the living architecture corpus against the code: the model reads docs/architecture/ plus the code and lists divergences with coordinates. Advisory only — an opinion of the model, never a verified verdict, no gates and no stamps. Nothing is applied automatically: corpus edits are a…
roadmap
An implementation plan made from a technical specification, organized into phases, milestones, and dependencies.