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 scoping-the-simplest-coregit 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/scoping-the-simplest-core)<a href="https://agentmods.dev/skills/prime-radiant-inc/iterative-development/scoping-the-simplest-core"><img src="https://agentmods.dev/badge/skills/prime-radiant-inc/iterative-development/scoping-the-simplest-core/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/scoping-the-simplest-core"><img src="https://agentmods.dev/badge/skills/prime-radiant-inc/iterative-development/scoping-the-simplest-core.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.00048 | $0.01487 |
| Opus 5 | $0.00024 | $0.00744 |
| Sonnet 5 | $0.00010 | $0.00297 |
| Haiku 4.5 | $0.00005 | $0.00149 |
Grade A, and why
scoping-the-simplest-core 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scoping the Simplest Core
Overview
Reads the per-epic requirement files in docs/superpowers/iterations/requirements/ and docs/superpowers/iterations/behavior-scenarios.md, and produces docs/superpowers/iterations/roadmap.md: a walking-skeleton iteration (ITER-0000) plus ordered follow-on iterations. The walking skeleton must produce the first runnable journey scenario. Runs citation and scope review via PAR before committing the roadmap.
When to Use
Invoked by iterative-development during bootstrap after extracting-requirements.
Script Location
All scripts referenced below live in this skill's scripts/ directory, next to this SKILL.md file.
Scoping Process
1. Read the backlog
Read the epic files in docs/superpowers/iterations/requirements/ — scan epic headers and story titles first, then dip into specific epic files for ACs when selecting.
Also read docs/superpowers/iterations/behavior-scenarios.md to understand which scenarios exist and which stories they cover.
2. Define the walking skeleton (ITER-0000)
Select a small cohesive set of stories from as many distinct epics as possible. The walking skeleton should prove the end-to-end shape of the product works.
Scenario requirement: the walking skeleton MUST include stories that close at least ONE journey scenario chain. Prefer the core product journey (e.g., "normal dictation" over "debug investigation"). The skeleton is not done until that journey scenario is runnable as an automated or scripted-reproducible test.
The walking skeleton must also produce:
- The first stable scenario IDs
- The first executable behavior harness (the E2E test infrastructure)
- A small sentinel corpus that can be rerun every iteration
Harness-first task: The walking skeleton's FIRST task should be designing and building the E2E test harness — before implementing any product features. Use the test infrastructure checklist in skills/shared/behavior-evidence-formats.md to guide the design. Document the harness design decisions in the project's docs. The harness is a first-class deliverable, not an afterthought — every subsequent iteration extends it.
What ships with it
2 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 · 136 lines · 48 tokens per session scan A afed46989c3d
scoping-the-simplest-core 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 48 tokens to every session and 1,487 once invoked, about $0.0002 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.