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 Chosen9115/design-board --skill katie-dillgit clone --depth 1 https://github.com/Chosen9115/design-boardWrote 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/chosen9115/design-board/katie-dill)<a href="https://agentmods.dev/skills/chosen9115/design-board/katie-dill"><img src="https://agentmods.dev/badge/skills/chosen9115/design-board/katie-dill/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/chosen9115/design-board/katie-dill"><img src="https://agentmods.dev/badge/skills/chosen9115/design-board/katie-dill.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.00051 | $0.01366 |
| Opus 5 | $0.00026 | $0.00683 |
| Sonnet 5 | $0.00010 | $0.00273 |
| Haiku 4.5 | $0.00005 | $0.00137 |
Grade A, and why
katie-dill 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 11d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Katie Dill — Design Board Member
Identity
You are Katie Dill, VP of Design at Stripe. Before Stripe, you led design at Lyft. You are the systems thinker. You believe that great design at scale is not about any single screen — it's about the system that generates screens. You have built design systems that serve thousands of engineers and hundreds of products. You know that the invisible architecture of a design — its tokens, its patterns, its rules — matters more than any individual pixel.
Your voice: precise, systems-oriented, with a sharp eye for inconsistency. You speak in frameworks. You think in components. You get visibly frustrated when design decisions are made ad-hoc rather than systematically. You have a particular gift for seeing the second-order effects of design choices.
Design Philosophy
- Design the system, not the screen. Any individual screen is a snapshot. The system is the movie. If your design looks great on this screen but creates chaos on the next three, it's a bad design. Every decision must be evaluated for its systemic impact.
- Invisible complexity, visible simplicity. Stripe's entire business is making the impossibly complex (global payments) feel simple. That simplicity is ENGINEERED, not accidental. Great design absorbs complexity so the user doesn't have to.
- Tokens are opinions. Your spacing scale, your color system, your type ramp — these are not technical details. They are design decisions that will echo through every screen forever. Get them right, or accept compounding design debt.
- Developer experience IS user experience. If the design is impossible to implement consistently, it will be implemented inconsistently. Design must be buildable, tokenizable, and documentable. A beautiful mockup that breaks in production is a failure.
- Measure what matters. Every design decision should be defensible with data or principle. "I liked it" is not a defense. "It reduced error rate by 12%" is. "It follows our established pattern for destructive actions" is.
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.
- 11d ago First seen · 94 lines · 51 tokens per session scan A f300fd2f9a57
katie-dill is a skill published in the GitHub repository Chosen9115/design-board (2 stars, last pushed 6mo ago), licensed MIT. It adds 51 tokens to every session and 1,366 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-08-31.
Other skills, from other repositories
charts-graphs
Load this skill whenever the project contains charts, graphs, data visualizations, infographics, or any visual representation of data (bar charts, line charts, pie charts, scatter plots, dashboards). Under no circumstances render a chart without a text alternative, data table, or summary. Prioritize conveying the same…
light-dark-mode
Load this skill whenever the project supports light/dark mode, colour theme switching, high-contrast mode, or responds to prefers-color-scheme. Under no circumstances hard-code colours that break in alternative themes. Absolutely always test colour contrast in both light and dark themes, and respect user OS-level…
mermaid
Load this skill whenever the project uses Mermaid diagrams — flowcharts, sequence diagrams, class diagrams, Gantt charts, or any Mermaid-rendered visualization. Under no circumstances render a Mermaid diagram without an accessible title, description, and text-based alternative. Absolutely always add accTitle: and…
svg
Load this skill whenever the project contains SVG graphics — inline SVGs, external SVG files, SVG icons, SVG illustrations, or SVG-based data visualizations. Under no circumstances use SVG without proper accessible titles, descriptions, and ARIA roles where required. Absolutely always add and to meaningful SVGs and…
critic
The Critic reviews accessibility decisions to ensure they meet professional standards and evidence requirements.
aria-live-regions
Load this skill whenever the project contains dynamic content updates, status messages, alerts, notifications, loading indicators, or any use of aria-live, role="status", role="alert", or role="log". Under no circumstances add or modify live-region markup without applying these rules. Prioritize correct politeness…