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 isvlasov/rageatc-oss --skill designing-interfacesgit clone --depth 1 https://github.com/isvlasov/rageatc-ossWrote 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/isvlasov/rageatc-oss/designing-interfaces)<a href="https://agentmods.dev/skills/isvlasov/rageatc-oss/designing-interfaces"><img src="https://agentmods.dev/badge/skills/isvlasov/rageatc-oss/designing-interfaces/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/isvlasov/rageatc-oss/designing-interfaces"><img src="https://agentmods.dev/badge/skills/isvlasov/rageatc-oss/designing-interfaces.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.00039 | $0.02522 |
| Opus 5 | $0.00019 | $0.01261 |
| Sonnet 5 | $0.00008 | $0.00504 |
| Haiku 4.5 | $0.00004 | $0.00252 |
Grade A, and why
designing-interfaces 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Designing Interfaces
Defines how the software should look and feel before any UI code is written. The orchestrator runs this directly (not delegated) — the work is dialogic, exploring the product's world with the user.
Position: architecting-software (ARCHITECTURE.md) → designing-interfaces (system.md) → decomposing-work (ROADMAP.md).
Inputs: confirmed PRD.md and ARCHITECTURE.md, and the user available for dialogue — design direction requires conversation, not assumption. Brownfield also needs the path to existing UI code.
Output: .interface-design/system.md — the persistent design record. Once created, all UI work references it; updates happen through this skill, not ad hoc edits.
Not covered: UI implementation (developer-agent's job), design compliance review during builds (the design-compliance review perspective), marketing design or landing pages, architecture and technology selection (architecting-software).
The Problem
You will generate generic output. Your training has seen thousands of dashboards; you can follow the entire process below — explore the domain, name a signature, state your intent — and still produce a template. Warm colours on cold structures. "Kitchen feel" that looks like every other app. Intent lives in prose, but code generation pulls from patterns, and the gap between them is where defaults win. The process helps; it does not guarantee craft. You have to catch yourself.
Defaults disguise themselves as infrastructure — the parts that feel like they just need to work, not be designed:
- Typography feels like a container. It is not holding your design — it IS your design. A bakery tool and a trading terminal both need "clean, readable type", but warm-and-handmade is not cold-and-precise.
- Navigation feels like scaffolding. It is not around your product — it IS your product: where you are, where you can go, what matters most.
- Data feels like presentation. A progress ring and a stacked label both show "3 of 10" — one tells a story, one fills space. Ask what the number means to the person looking at it.
- Token names feel like implementation detail.
--inkand--parchmentevoke a world;--gray-700and--surface-2evoke a template.
What ships with it
7 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 · 171 lines · 39 tokens per session scan A a9d61acd53af
designing-interfaces is a skill published in the GitHub repository isvlasov/rageatc-oss (9 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 2,522 once invoked, about $0.0002 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
design-method
Use when starting any design task — resolves register, sets the 3 dials, locks Gate 0, and routes to the right move and target skill.
design-webapp
Use when building or extending a dashboard, SaaS screen, or any authenticated app surface — use design-web instead for a marketing site.
design-web
Use when building or revising a marketing/landing/campaign page, register brand locked at Gate 0 — use design-webapp for app screens instead.
design-motion
Use when adding or reviewing motion on an already-settled layout or component — never to hide or compensate for an unfinished one.
design-review
Use when a design deliverable is about to be reported done — the final quality gate after design-motion or a mobile mockup.
design-android
Use when designing an Android screen or flow — deliverable is a device-framed HTML mockup and developer handoff spec, never Compose code.