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 skills add vasuag09/harness-claude --skill designgit clone --depth 1 https://github.com/vasuag09/harness-claudeWrote 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/skills/vasuag09/harness-claude/design)<a href="https://agentmods.dev/skills/vasuag09/harness-claude/design"><img src="https://agentmods.dev/badge/skills/vasuag09/harness-claude/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/skills/vasuag09/harness-claude/design"><img src="https://agentmods.dev/badge/skills/vasuag09/harness-claude/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.00080 | $0.01063 |
| Opus 5 | $0.00040 | $0.00531 |
| Sonnet 5 | $0.00016 | $0.00213 |
| Haiku 4.5 | $0.00008 | $0.00106 |
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 9d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/design — product/UX design brief
Goal: decide what this should look like and how it should behave before code, so design
isn't improvised inside /harness-claude:implement (where it comes out worst). The product-design
counterpart to /harness-claude:architect (system design). Both are conditional PLAN steps —
a change can need one, both, or neither.
When to use
Only when the change has a user-facing surface — a page, screen, component, dashboard,
form, email, or CLI/TUI presentation a human looks at. If the work is internal/back-end
(an API, a script, a refactor with no visible change), skip and say so — like
/harness-claude:architect skips routine work. The harness itself (a CLI plugin) skips this step.
Do this
1. Route by surface
Pick the leading craft rubric from the change's surface, then always overlay the floor:
| Surface | Lead rubric |
|---|---|
| Product UI — dashboard, admin, SaaS, tool, settings, data | references/product-ui.md |
| Marketing / brand / landing / portfolio / expressive | references/aesthetic-direction.md |
| Mobile / native (iOS/Android, React Native, Flutter) | references/ux-floor.md (+ closest of the two above) |
| Every surface (overlay, not optional) | references/ux-floor.md |
Read the leading rubric(s) under skills/design/references/. These are the harness's own design
standard and are fully self-contained — no external plugin or install is required. If the project
keeps a saved design-system note (e.g. .design/system.md), read it too and hold to its decisions.
2. Explore before proposing (don't default)
Per the lead rubric: name the human (who, where, what they did 5 min before/after), the task (the verb), and the feel (in words that mean something). For product/marketing, do the domain exploration — domain · color-world · signature · the 3 defaults you're rejecting. Test: remove the product name from your proposal — could someone still tell what it's for?
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 75 lines · 80 tokens per session scan A 5c464fc53bbe
design is a skill published in the GitHub repository vasuag09/harness-claude (2 stars, last pushed 2mo ago), licensed MIT. It adds 80 tokens to every session and 1,063 once invoked, about $0.0004 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 skills, from other repositories
frontend-taste
Premium frontend design skills that override LLM defaults. Prevents generic 'AI-looking' UI. Enforces deterministic typography, calibrated color, asymmetric layouts, spring physics, hardware-accelerated motion. Triggers: 'UI tasarla', 'design a UI', 'premium landing page', 'frontend taste', 'anti-slop', 'dashboard…
design-tokens
Project-level DESIGN.md tokens reference. When the project has a DESIGN.md file, agents producing UI / components / visuals must consult this skill to use canonical color/typography/spacing tokens rather than inventing new ones. Triggers on: UI generation, component creation, design brief, visual asset, tailwind…
stitch-design-taste
Semantic Design System Skill for Google Stitch. Generates agent-friendly DESIGN.md files that enforce premium, anti-generic UI standards — strict typography, calibrated color, asymmetric layouts, perpetual micro-motion, and hardware-accelerated performance.
design
UI/UX, visual hierarchy, typography, color theory, design systems, accessibility, and prototyping skills. From wireframes to production-ready interfaces with research-backed decisions. Triggers on: UI, UX, design system, typography, color palette, wireframe, prototype, accessibility, visual hierarchy.
design-taste-frontend
Senior UI/UX Engineer. Architect digital interfaces overriding default LLM biases. Enforces metric-based rules, strict component architecture, CSS hardware acceleration, and balanced design engineering.
redesign-existing-projects
Upgrades existing websites and apps to premium quality. Audits current design, identifies generic AI patterns, and applies high-end design standards without breaking functionality. Works with any CSS framework or vanilla CSS.