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 agentmods add skills/ericrisco/rsc-harness/designnpx skills add ericrisco/rsc-harness --skill designgit clone --depth 1 https://github.com/ericrisco/rsc-harnessWrote 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/ericrisco/rsc-harness/design)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/design"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/design.svg" alt="Measured on agentmods" 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 | $0.00100 | $0.06781 |
| Opus 5 | $0.00050 | $0.03390 |
| Sonnet 5 | $0.00020 | $0.01356 |
| Haiku 4.5 | $0.00010 | $0.00678 |
Grade C, and why
design scanned grade C with 1 finding 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 yesterday.
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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Bad — magic hex + arbitrary px, no system --> How it starts
The opening of the file, as written. The whole thing — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design — Product UI, Landing Pages & Conversion Copy
Hand-off — the visual system vs the craft of motion. This skill owns the visual system and page
composition, and sets motion intent + budget only. The implementation of an animation is
../motion-craft/SKILL.md's; how a piece of interface should be BUILT — boundaries, state, the
loading and empty and error states — is ../ui-engineering/SKILL.md's. When a request could belong to
several of those, start from the one that owns the decision, not the one that owns the file. The motion reference in
this skill defers its mechanics to them rather than restating them.
Research the best current work, then ship a premium, accessible, fast, high-converting interface.
SDD gate. If this fired on a new, non-trivial feature or behaviour change and there is no approved spec + plan under
02-DOCS/wiki/sdd/, hand off to../specify/SKILL.mdfirst — it runs brainstorm → spec → plan → tasks before any code, then routes back here once the plan is approved. Build straight from here only for a genuinely one-line / low-risk change. Method:../sdd/SKILL.md.
Hand-offs. The WORDS are ../marketing/SKILL.md's: it co-owns the 02-DOCS/wiki/brand/ study (the words dimensions there, the visual ones here), and deep keyword research, GEO, or a technical SEO audit belongs to it — this skill only enforces SEO-aware structure in markup. The BUILD (App Router / React 19) is ../nextjs/SKILL.md's. Mirroring the brand tokens into a Flutter app is ../flutter/SKILL.md's. Pure backend/data/infra with no UI surface: decline — there is nothing to design. Three references live outside this repo and are named for direction only, not invocable here: frontend-design-direction for dense internal tooling used daily (never paint a marketing skin on a tool that needs repeated daily use — fold its judgment in via the DIRECTION BRIEF); liquid-glass-design for native iOS 26 SwiftUI Liquid Glass (this skill ships the web glass approximation only); motion-ui / motion-foundations for motion-code mechanics (springs, AnimatePresence internals, layout animations — this skill sets motion intent + budget).
What ships with it
15 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.
- evals/cases.yaml 6.0 KB
- evals/README.md 2.9 KB
- references/ai-tells.md 4.4 KB
- references/brand-grounding.md 13 KB
- references/copywriting-frameworks.md 6.9 KB
- references/design-systems.md 3.4 KB
- references/inspiration-sources.md 6.2 KB
- references/landing-anatomy-and-cro.md 9.1 KB
- references/motion-and-interaction.md 11 KB
- references/research-method.md 9.7 KB
- references/signature-and-craft.md 10 KB
- references/starting-point.md 5.2 KB
- references/trends-2026.md 6.9 KB
- references/visual-system.md 11 KB
- scripts/verify.sh 17 KB runs code
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.
- yesterday First seen · 361 lines · 100 tokens per session scan C 3d1a80053489
design is a skill published in the GitHub repository ericrisco/rsc-harness (64 stars, last pushed 2d ago), licensed MIT. It adds 100 tokens to every session and 6,781 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
webd
Web design workflow for landing pages, SaaS frontends, conversion-oriented pages, and non-generic UI. Use when building or improving a website, landing page, SaaS UI, hero section, pricing page, conversion funnel, shadcn/ui interface, or when the user invokes /webd or @webd.
moai-design-tools
Design tool integration specialist covering Figma MCP, Pencil renderer, and Pencil-to-code export. Use when fetching design context from Figma, rendering Pencil designs, or exporting to React/Tailwind code.
moai-ref-ui-polish
UI polish and interface-completion reference: the small visual details — concentric border radius, optical alignment, shadow-vs-border, motion easing, typography smoothing, tabular numbers, icon stroke weight, hit areas — that separate polished interfaces from generic ones. Agent-extending skill that amplifies…
qa-design
UI/UX design audit and verification of web best practices, including responsive/mobile-first breakpoints. Trigger when the user wants to audit the design, verify the UI/UX, check responsive behaviour, or improve the user interface.
dev-frontend-design
Distinctive UI design with strong art direction. Trigger when the user wants to create an interface, a landing page, a visual component, or when frontend code creation is detected without a defined design direction.
dev-shadcn
Integration and customization of shadcn/ui (copy-paste React components, Radix + Tailwind). Trigger when the user wants to install shadcn, add components, customize the theme, or when shadcn/ui usage is detected in the project.