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 openplanr/planr-pipeline/plugin install 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/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/openplanr/planr-pipeline/design-loop"><img src="https://agentmods.dev/badge/commands/openplanr/planr-pipeline/design-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.00040 | $0.01019 |
| Opus 5.5 | $0.00016 | $0.00408 |
| Sonnet 5.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 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.
This is a copy
100% identical to design-loop — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 1mo 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 28d ago), licensed MIT. It adds 40 tokens to every session and 1,019 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to design-loop, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
verify
Fidelity check — rebuild a page from the extracted tokens, pixel-diff it against the live site, and score how faithfully the tokens capture the design.
design-tutorial
Interactive guided tour of Naksha — learn commands through real exercises, discover workflows, and get oriented in under 10 minutes.
ux-audit
Audit a Figma file against a design brief — checks page structure, frame naming, sizes, styles, components, and content compliance.
iteration-loop
Run a whole iteration Phase 1→6 autonomously — code-first direction lock with a retained prototype, then execute → close → PR → merge-ready → post-merge close. Optional direction hint and scale S|M|L|XL; explicit autonomous opt-in, no grill-me, no routine confirmation.
amazing-e2e-check
Run explicitly requested E2E, browser, device, or installed-deployment scenarios in an independent verification workflow.
ccc-theme
List, preview or switch the Commander terminal color theme (Claude, OLED Black, Matrix, or a random palette) used by hooks and terminal art. Use when the user asks to change the theme, colors or skin.