Borrowing it
Nothing to install: this file belongs to luanmorenommaciel/agentspec. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/luanmorenommaciel/agentspec/main/.claude/commands/workflow/iterate.mdgit clone --depth 1 https://github.com/luanmorenommaciel/agentspecWrote 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/commands/luanmorenommaciel/agentspec/iterate)<a href="https://agentmods.dev/commands/luanmorenommaciel/agentspec/iterate"><img src="https://agentmods.dev/badge/commands/luanmorenommaciel/agentspec/iterate/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/commands/luanmorenommaciel/agentspec/iterate"><img src="https://agentmods.dev/badge/commands/luanmorenommaciel/agentspec/iterate.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.00016 | $0.00569 |
| Opus 5.5 | $0.00006 | $0.00228 |
| Sonnet 5.5 | $0.00003 | $0.00114 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
iterate 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 1mo 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Iterate Command
Update any phase document when requirements or design changes (Cross-Phase)
Usage
/iterate <file> "<change-description>"
Examples
/iterate BRAINSTORM_SEARCH_API.md "Consider ElasticSearch instead of PostgreSQL full-text search"
/iterate DEFINE_SEARCH_API.md "Add support for fuzzy matching, not just exact search"
/iterate DESIGN_SEARCH_API.md "Services need to be self-contained, no shared common/"
/iterate .claude/sdd/features/DEFINE_AUTH.md "Change from JWT to session-based auth"
What This Command Works On
/iterate updates the document phases of the SDD workflow:
Phase 0: /brainstorm → BRAINSTORM_{FEATURE}.md ← /iterate can update
Phase 1: /define → DEFINE_{FEATURE}.md ← /iterate can update
Phase 2: /design → DESIGN_{FEATURE}.md ← /iterate can update
Phase 3: /build → (code) ← update DESIGN, then /build
Phase 4: /ship → (archive) ← N/A
Important: to change code during Phase 3, update the DESIGN document first — the cascade to
code triggers a rebuild via /build. This ensures traceability.
Scope check: more than ~50% change, a different problem, or different target users is a new
/define, not an iterate — the skill carries the thresholds.
What Happens
- Load the skill — read
.claude/skills/sdd-iterate/SKILL.md; it owns the full methodology. - Classify the change — additive, modifying, removing, or architectural, with impact level.
- Analyze cascades — walk the downstream documents (BRAINSTORM → DEFINE → DESIGN → CODE) for required updates.
- Confirm with the user — present the cascade options; never apply cascading edits silently.
- Apply — update the target (and confirmed downstream documents) with version bumps and change notes.
Output
| Artifact | Location |
|---|---|
| Updated document | Same location as input |
| Cascade updates | Downstream documents (if confirmed) |
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.
- 1mo ago First seen · 75 lines · 16 tokens per session scan A 69e229b6837d
iterate is a command published in the GitHub repository luanmorenommaciel/agentspec (256 stars, last pushed 3d ago), licensed MIT. It adds 16 tokens to every session and 569 once invoked, about $0.0001 per session on Opus 5.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-01.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
sync-linear
Sync current work with Linear ticket status.
plc-project-status
Read .claude/skills/plc-project-status/SKILL.md and execute its official procedure. Target: $ARGUMENTS.