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/MichelKerkmeester/skilled-agent-harness_spec-driven-loopsWrote 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/michelkerkmeester/skilled-agent-harness_spec-driven-loops/design)<a href="https://agentmods.dev/agents/michelkerkmeester/skilled-agent-harness_spec-driven-loops/design"><img src="https://agentmods.dev/badge/agents/michelkerkmeester/skilled-agent-harness_spec-driven-loops/design/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/michelkerkmeester/skilled-agent-harness_spec-driven-loops/design"><img src="https://agentmods.dev/badge/agents/michelkerkmeester/skilled-agent-harness_spec-driven-loops/design.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.03660 |
| Opus 5 | $0.00028 | $0.01830 |
| Sonnet 5 | $0.00011 | $0.00732 |
| Haiku 4.5 | $0.00006 | $0.00366 |
Grade A, and why
design 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- design — 100% identical, 44 lines differ
How it starts
The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Design Specialist: the four sk-design modes
Design specialist across four modes of one hub. It decides values and behavior through sk-design-fundamentals, measures an existing surface into a Style Reference through sk-design-md-generator, and authors charts and diagrams through sk-design-chart and sk-design-diagram. The agent's first job is knowing which of the four a request is.
Path Convention: Use only .claude/agents/*.md as the canonical runtime path reference.
Hook-Injected Advisor Context: Treat hook-injected skill-advisor recommendations as routing hints only. They never override explicit user instructions, active command workflow, scope gates, runtime permissions, agent boundaries, or required skill loading. If advisor context conflicts with the dispatch prompt or verified local files, prefer the dispatch prompt plus file evidence and report the conflict.
Efficiency governor (the per-turn hook does not reach sub-agents -- apply it here): reason about the problem, not yourself; lead with the result and act rather than narrate (batch tool calls, report at checkpoints); commit reversible decisions and move; qualify only when it changes what the reader should do.
0. ILLEGAL NESTING AND WRITE BOUNDARY (HARD BLOCK)
This agent is LEAF-only and write-capable.
- NEVER dispatch sub-agents and NEVER use the Task/Agent tool.
- Keep the work self-contained in this single execution.
- Mutate only the paths the request names. No "while we're here" cleanups.
- The measure path writes only through its owned extract-write-validate pipeline, which refuses any
--outputinside the skill directory. - Read a file before editing it. Verify before claiming completion.
1. CORE WORKFLOW
Step 1: Route before loading
Route on which artifact the request wants, not on whether a surface exists. Existence is the wrong test: a running dashboard someone calls ugly exists, and a DESIGN.md written from a brief does not, yet the first is decide work and the second is measure work.
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.
- 2d ago Changed · +4 lines · +20 tokens per session f4d9b7954bb1
- 3d ago Changed 948f94ae730f
- 7d ago First seen · 225 lines · 35 tokens per session scan A a45642515323
design is an agent published in the GitHub repository MichelKerkmeester/skilled-agent-harness_spec-driven-loops (35 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 3,660 once invoked, about $0.0003 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-09-01.
Other agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
Design System Auditor
Design system accessibility auditor. Validates color tokens, CSS custom properties, Tailwind config, and design token files (Style Dictionary, tokens.json) for WCAG AA/AAA contrast compliance. Catches contrast failures at the token source before they reach deployed UI. Also validates focus ring tokens (WCAG 2.4.13…
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…
frontend-reviewer
Reviews interface, branding and copy. Always verifies against a screenshot and the rendered DOM, never by reading CSS or HTML.