Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ShipWithAI/shipwithai-pluginsnpx agentmods add commands/shipwithai/shipwithai-plugins/ui-iterateWrote 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/shipwithai/shipwithai-plugins/ui-iterate)<a href="https://agentmods.dev/commands/shipwithai/shipwithai-plugins/ui-iterate"><img src="https://agentmods.dev/badge/commands/shipwithai/shipwithai-plugins/ui-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/shipwithai/shipwithai-plugins/ui-iterate"><img src="https://agentmods.dev/badge/commands/shipwithai/shipwithai-plugins/ui-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.00043 | $0.01424 |
| Opus 5.5 | $0.00017 | $0.00570 |
| Sonnet 5.5 | $0.00009 | $0.00285 |
| Haiku 4.5 | $0.00004 | $0.00142 |
Grade A, and why
ui-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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Iterate on $ARGUMENTS until it passes, then stop. Hard cap: 4 iterations, then escalate to the human.
Two lanes, kept apart. You are the executor: you edit the @Composable and run the gates. The evaluator is a separate subagent in a fresh context (step 4) — never grade your own edits, that's the self-review this loop exists to prevent.
Commands below use placeholders (
<app-module>,<module>,<your.pkg>) ande.g.examples. Derive the real values from this project in step 0 — never run the example coordinates verbatim.
0. Locate + resolve target
Globfor the screen's inspection test:**/*$ARGUMENTS*Inspection.kt(convention:<Screen>Inspection, seeded by thesetupskill). From its path derive three things: the Gradle module (e.g.:feature:foo:impl), the test FQN (e.g.com.acme.feature.foo.impl.presentation.<Screen>Inspection), and the PNG dir (<module>/build/outputs/roborazzi/).- No inspection test yet? Create one from the template the
setupskill installs (assets/substrate/ScreenInspection.kt.tmpl; see INTEGRATION.md) — width {360,411} × fontScale {1.0,1.5,2.0} × {light,dark} × content {default,long,empty,error}, each capturing to_inspect_*.pngthen callingTier1Assertions.assertAll. - Target: if
harness/targets/$ARGUMENTS.pngexists → Fidelity mode (evaluator reports deltas vs target). Else → absolute rubric mode.
1. Implement / edit (executor lane)
Edit the @Composable for $ARGUMENTS. Rails (apply whichever your project has):
- Reuse your design system — check your component catalog before building anything new.
- Tokens, not literals — use your theme's color/spacing/type/shape tokens (keep raw
MaterialTheme.*inside the design-system module). - Insets: top-level screens consume
WindowInsets(status/nav bars, IME). - Boundary gate: if your project enforces a design-system / Material-3 boundary (e.g. via the
konsist-architecture-testsskill or a Konsist rule), satisfy it — add or reuse a wrapper rather than importing the gated API directly.
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 · 71 lines · 43 tokens per session scan A 308236b85805
ui-iterate is a command published in the GitHub repository ShipWithAI/shipwithai-plugins (9 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 1,424 once invoked, about $0.0002 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-08-31.
Other commands, from other repositories
loop
Autonomous execution loop. Runs the TDD cycle repeatedly until all tasks in an epic are complete, with circuit breaker protection and PR workflow.
review-skills
Review changed skills: automated bash checks + 9 structural dimensions (D1-D9) + 5 intent checks (M1-M5). PASS/FAIL verdict. Fix in-place.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
ccc-feature-start
Kick off a feature: research context, create an isolated branch, confirm a green baseline, write a task breakdown, and the first failing test. Use when starting new feature work in a git repository.
ccc-audit
Audit the current project for dependency vulnerabilities, oversized bundles, type errors, dead code, hardcoded secrets, undocumented env vars and a missing CLAUDE.md. Use when you want a health score before a release or review.
impact
Which tests a change impacts, with a ready-to-run test command.