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.
git clone --depth 1 https://github.com/qGolem/orcWrote 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/agents/qgolem/orc/design-iterator)<a href="https://agentmods.dev/agents/qgolem/orc/design-iterator"><img src="https://agentmods.dev/badge/agents/qgolem/orc/design-iterator/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/agents/qgolem/orc/design-iterator"><img src="https://agentmods.dev/badge/agents/qgolem/orc/design-iterator.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.00055 | $0.04918 |
| Opus 5.5 | $0.00022 | $0.01967 |
| Sonnet 5.5 | $0.00011 | $0.00984 |
| Haiku 4.5 | $0.00006 | $0.00492 |
Grade A, and why
design-iterator 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 — 416 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert UI/UX design iterator specializing in systematic, progressive refinement of web components. Your methodology combines visual analysis, competitor research, and incremental improvements to transform ordinary interfaces into polished, professional designs.
Core Methodology
For each iteration cycle, you must:
- Take Screenshot: Capture ONLY the target element/area using focused screenshots (see below)
- Analyze: Identify 3-5 specific improvements that could enhance the design
- Implement: Make those targeted changes to the code
- Document: Record what was changed and why
- Repeat: Continue for the specified number of iterations
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 · 416 lines · 55 tokens per session scan A 900d8768c669
design-iterator is an agent published in the GitHub repository qGolem/orc (5 stars, last pushed 7mo ago), licensed MIT. It adds 55 tokens to every session and 4,918 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 agents, from other repositories
ui-analyzer
Gathers decision-relevant UI facts from recorded external resources and the existing codebase. Use when frontend design needs compact evidence before UI Spec or Design Doc creation.
ui-spec-designer
Creates UI Specifications from confirmed requirements and optional prototype code. Use when frontend UI design is needed, or when "UI spec/screen design/component decomposition/UI specification" is mentioned.
work-planner
Creates implementation-focused work plans from approved Design Docs. Use when Design Doc is complete and implementation planning is needed, or when "work plan/implementation plan/task planning" is mentioned.
evolve-accessibility-audit
Accessibility audit agent for the Evolve Loop (Evaluate archetype). The advisor INSERTS this phase after build whenever scout.goaltype == "accessibility" to adversarially review changed UI/HTML/React against WCAG 2.1/2.2 AA.
evolve-frontend-design-review
Adversarial frontend design review agent for the Evolve Loop (Evaluate archetype). The advisor INSERTS this phase after Build whenever scout.goaltype == "frontend-ui", to judge changed UI for production-grade design quality and BLOCK on design-system violations or broken responsive states.
ux-designer
Expert UX Designer with 30 years of experience in user experience and product design. Provides UX strategy, design critique, and usability guidance. Advisory only - does not modify code.