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 agentmods add commands/openplanr/planr-pipeline/design-loopgit clone --depth 1 https://github.com/openplanr/planr-pipelineWrote 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/openplanr/planr-pipeline/design-loop)<a href="https://agentmods.dev/commands/openplanr/planr-pipeline/design-loop"><img src="https://agentmods.dev/badge/commands/openplanr/planr-pipeline/design-loop.svg" alt="Measured on agentmods" 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 | $0.00040 | $0.01019 |
| Opus 5 | $0.00020 | $0.00509 |
| Sonnet 5 | $0.00008 | $0.00204 |
| Haiku 4.5 | $0.00004 | $0.00102 |
Grade A, and why
design-loop 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 4d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/planr-pipeline:design-loop {target}
The generalized design shotgun: concept list → confirm before any spend → N parallel variants → a live localhost board (the board is the chooser; chat is only the wait) → file-handshake feedback (pins on exact regions, ratings, remix) → session-chained iteration → approval → taste memory. Works with an OpenAI key (image generation) and without one (claude-svg: agent-authored SVG — for logos/UI often better: exact hex, real type, vector output).
Engine: ${CLAUDE_PLUGIN_ROOT}/lib/design-engine/cli.mjs (node <abs-path> <cmd> …).
Resolve PLUG exactly as design-step2-generate.md C.1 does (this file's path minus
/commands/design-loop.md); always substitute absolute paths — shell vars don't reach
subagents (hard rule 6).
R1: this loop STOPS at approval. It never auto-chains into /plan or /ship.
Sharing is explicit: the board's Share control creates an immutable multi-variant
artifact review only when the user selects it. Opening the board, submitting feedback,
regenerating, or approving never publishes anything. A remote reviewer returns a new review
URL; bring it back with planr artifact import "<returned-review-url>". Importing feedback is
also explicit and never advances PLAN → SHIP.
Task tracking
Create one task per phase (TaskCreate, advance with TaskUpdate; pre-2.1.142 runtimes:
TodoWrite; no task tool: inline). Verify each phase's outputs on disk before advancing.
Phase A — Context + taste + conceptsPhase B — Concept gate (no spend before confirm)Phase C — Parallel variant generationPhase D — Board loop (feedback → iterate)Phase E — Approve + taste + handoff
Phases (execute in order)
| Phase | Procedure |
|---|---|
| A — context, taste read, concept list | ${CLAUDE_PLUGIN_ROOT}/procedures/design-loop-step0-context.md |
| B — the concept gate | ${CLAUDE_PLUGIN_ROOT}/procedures/design-loop-step1-gate.md |
| C — parallel variants | ${CLAUDE_PLUGIN_ROOT}/procedures/design-loop-step2-variants.md |
| D — board + iteration loop | ${CLAUDE_PLUGIN_ROOT}/procedures/design-loop-step3-board.md |
| E — approve, taste, handoff | ${CLAUDE_PLUGIN_ROOT}/procedures/design-loop-step4-approve.md |
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.
- 4d ago First seen · 70 lines · 40 tokens per session scan A 44b4ffa902fd
design-loop is a command published in the GitHub repository openplanr/planr-pipeline (2 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 1,019 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-31.
Other commands, from other repositories
iteration-loop
Autonomous full iteration loop for cloud agents — Phase 1 (code-first auto direction lock + compass/plans + Review & Edit chain) through Phase 2–5 (execute → close → PR → merge-ready). Optional args: direction, scale (S|M|L|XL, default M). Not Done until Phase 5 exit checklist passes. Minimal human intervention; no…
iteration-drive
Drive the active iteration to completion — Phase 2 Autonomous Execute, Phase 3 iteration-close, Phase 4 Create PR, Phase 5 PR merge-ready loop (prefer babysit/-babysit; optional greploop when repo has it; else CI fallback) until mergeable. Not Done until Phase 5 exit checklist passes.
codebase-audit
Survey a codebase as a senior advisor and produce prioritized, self-contained improvement plans. Read-only on source code. Use standalone before iteration-start to discover what's worth doing, or independently to build a prioritized backlog.
document
Record a decision as an ADR or RFC, or document existing code as a spec, doc, guide, or rule; routes to the right document type.
init
First-time Archcore setup — detect the repo, compose the full first-day seed in one preview, create it on one confirm, and wire host configs.
cast
Run the Transmute pipeline — full build or specific stage.