Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Habib0x0/spec-driven-plugin/plugin install spec-drivenWrote 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/habib0x0/spec-driven-plugin/spec-loop)<a href="https://agentmods.dev/commands/habib0x0/spec-driven-plugin/spec-loop"><img src="https://agentmods.dev/badge/commands/habib0x0/spec-driven-plugin/spec-loop/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/habib0x0/spec-driven-plugin/spec-loop"><img src="https://agentmods.dev/badge/commands/habib0x0/spec-driven-plugin/spec-loop.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.00011 | $0.01532 |
| Opus 5.5 | $0.00004 | $0.00613 |
| Sonnet 5.5 | $0.00002 | $0.00306 |
| Haiku 4.5 | $0.00001 | $0.00153 |
Grade B, and why
spec-loop scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat .claude/specs/my-feature/progress.md | tail -20 How it starts
The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/spec-loop Command
Run spec-driven implementation in a loop. Each iteration picks the next highest-priority task, implements it, and continues until all tasks are done or max iterations reached.
Usage
Run the script directly from your project root:
${CLAUDE_PLUGIN_ROOT}/scripts/spec-loop.sh [--spec-name <name>] [--max-iterations <n>] [--progress-tail <n>] [--on-complete <command>]
Or via Bash tool if invoked within Claude Code:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/spec-loop.sh --spec-name <name>
Arguments
--spec-name <name>- Which spec to execute against. Auto-detected if only one spec exists in.claude/specs/.--max-iterations <n>- Maximum number of iterations before stopping. Default: 50.--progress-tail <n>- Number of recent progress entries to include in prompt. Default: 20.--on-complete <command>- Shell command to run after clean completion. Only fires when<promise>COMPLETE</promise>is detected, not on max-iterations exit. Recommended:"bash scripts/spec-accept.sh --spec-name <name>".
What It Does
- Reads your spec files fresh each iteration
- Runs Claude to implement one feature per iteration
- Runs verification gates on completed tasks
- Checks output for
<promise>COMPLETE</promise>to detect completion - Stops when all tasks are done or max iterations reached
Recommended hook — run UAT automatically on clean completion:
bash scripts/spec-loop.sh --spec-name <name> \
--on-complete "bash scripts/spec-accept.sh --spec-name <name>"
If you want docs too:
bash scripts/spec-loop.sh --spec-name <name> \
--on-complete "bash scripts/spec-accept.sh --spec-name <name> && bash scripts/spec-docs.sh --spec-name <name>"
Post-completion (release notes, retro) should be run manually after reviewing acceptance results:
bash scripts/spec-accept.sh --spec-name <name> # UAT gate
bash scripts/spec-docs.sh --spec-name <name> # Docs
bash scripts/spec-release.sh --spec-name <name> # Release notes
bash scripts/spec-retro.sh --spec-name <name> # Retrospective
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 · 180 lines · 11 tokens per session scan B 8a69b6549bd4
spec-loop is a command published in the GitHub repository Habib0x0/spec-driven-plugin (10 stars, last pushed 5mo ago), licensed MIT. It adds 11 tokens to every session and 1,532 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
re-review
Round 2+ review — confirm revisions landed, catch regressions, do not re-litigate.
review-plan
Unbiased review of another session's implementation plan.
review-spec
Unbiased review of another session's spec or design doc.
brief
Brief a PR, MR or the current branch with Punchcard — the reviewer's orientation before the review, never a review.
pr
Review a GitHub PR or GitLab MR with Punchcard and post the review into it.
scaffold-component
Scaffold a single named component from the architecture blueprint with production-depth code.