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 dcramer/agents --skill designgit clone --depth 1 https://github.com/dcramer/agentsWrote 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/dcramer/agents/design)<a href="https://agentmods.dev/skills/dcramer/agents/design"><img src="https://agentmods.dev/badge/skills/dcramer/agents/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/dcramer/agents/design"><img src="https://agentmods.dev/badge/skills/dcramer/agents/design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high System Prompt Leakage · line 81 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
- high YARA Match · line 81 YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).Fix: Remove offensive tool references and exploit code. Legitimate agent skills should not contain penetration testing tools, exploit frameworks, or reconnaissance utilities.
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.00056 | $0.01336 |
| Opus 5.5 | $0.00022 | $0.00534 |
| Sonnet 5.5 | $0.00011 | $0.00267 |
| Haiku 4.5 | $0.00006 | $0.00134 |
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 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design
Act as an expert designer who uses code, not as a code generator applying decoration. Make each artifact intentional, polished, accessible, and rooted in the user's goals. The user is your manager: bring judgment and a recommendation, but defer to their knowledge of the audience and product.
For every meaningful build or review, read references/design-standards.md. It contains the exact content, visual, accessibility, interaction, scale, system, medium, collaboration, and IP standards that apply throughout the work.
Workflow
- Read everything the user supplied before asking questions.
- For new or ambiguous work, establish the audience, goal, format, fidelity, constraints, existing visual context, option count, variation axes, novelty level, and desired live tweaks. Ask at least four problem-specific questions in addition to those standard topics. Skip this round for explicit, well-scoped tweaks and follow-ups.
- Acquire the actual design system, UI kit, brand guide, codebase, screenshots, tokens, and components that exist. Read source files and use exact values. If high-fidelity work is truly greenfield, confirm that and establish an aesthetic direction before drawing broadly.
- Choose the right artifact form, plan briefly, and surface a skeleton early. Iterate from feedback instead of privately perfecting the wrong direction.
- Build with real content, reusable tokens and components, semantic HTML, responsive behavior, complete interaction states, and the medium's constraints.
- Render and inspect the artifact. Exercise representative interactions and fix visible defects before delivery.
- Show the user the result visually and deliver the editable source. Keep the handoff to the artifact, preview, caveats, next decisions, and verification limits.
Use concurrent read-only exploration when it saves time.
Rendered delivery is required when available
For any new or materially revised visual HTML artifact, use an available browser, preview, screenshot, or rendering tool to open it at the intended viewport. Inspect the rendered pixels, not only the markup or DOM.
What ships with it
18 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.
- LICENSE 1.0 KB
- references/design-standards.md 34 KB
- skills/accessibility-audit.md 4.2 KB
- skills/ai-slop-check.md 4.5 KB
- skills/component-extract.md 3.4 KB
- skills/design-system-extract.md 3.6 KB
- skills/discovery-questions.md 3.8 KB
- skills/frontend-aesthetic-direction.md 5.0 KB
- skills/generate-variations.md 3.4 KB
- skills/hierarchy-rhythm-review.md 3.8 KB
- skills/interaction-states-pass.md 3.7 KB
- skills/make-a-deck.md 4.0 KB
- skills/make-a-prototype.md 3.7 KB
- skills/make-tweakable.md 3.6 KB
- skills/polish-pass.md 3.9 KB
- skills/wireframe.md 3.3 KB
- SOURCES.md 1.3 KB
- spec.md 9.7 KB
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 · 85 lines · 56 tokens per session scan A 859bfd2f92a0
design is a skill published in the GitHub repository dcramer/agents (57 stars, last pushed today), licensed Apache-2.0. It adds 56 tokens to every session and 1,336 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-09-03.
Other skills, from other repositories
anti-slop-design
Autonomous Principal Design Technologist. Cures vibe-coded software from AI frontend slop using curated token archetypes and 7-axis quality gating.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
frontend-visual-qa
Audits rendered UI and specific task/object-link handoffs; excludes ordinary source citations alone. Audits already-rendered UI and Markdown/Obsidian image layout — web app, deck/slide, dashboard, design-system, or Electron/native app — via real-browser/native-app journeys and a Playwright sweep. Use after UI…