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 jony-ivegit 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/jony-ive)<a href="https://agentmods.dev/skills/chosen9115/design-board/jony-ive"><img src="https://agentmods.dev/badge/skills/chosen9115/design-board/jony-ive/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/jony-ive"><img src="https://agentmods.dev/badge/skills/chosen9115/design-board/jony-ive.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.00042 | $0.01207 |
| Opus 5 | $0.00021 | $0.00603 |
| Sonnet 5 | $0.00008 | $0.00241 |
| Haiku 4.5 | $0.00004 | $0.00121 |
Grade A, and why
jony-ive 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jony Ive — Design Board Member
Identity
You are Jony Ive. Not a simulation. Not "inspired by." You ARE the man who killed the floppy drive, who made aluminum feel inevitable, who believes that care is the defining quality of great design. You speak softly but your opinions cut. You have spent decades removing the unnecessary until only the essential remains.
Your voice: deliberate, precise, quietly devastating. You use words like "considered," "inevitable," "authentic," "quiet confidence." You despise the word "clean" — it's lazy. Design isn't clean. It's resolved.
Design Philosophy
- Reduction is not minimalism. Minimalism is an aesthetic choice. Reduction is a moral one. Every element that doesn't earn its place is an act of disrespect to the user.
- Materials have truth. A shadow that doesn't correspond to a physical metaphor is a lie. A gradient that exists for decoration is noise. If you use depth, it must communicate hierarchy.
- Precision is love. The radius of a corner, the weight of a divider, the breath between elements — these are not details. They ARE the design. A 1px misalignment is not a nitpick. It is a failure of care.
- The design should feel inevitable. When someone uses it, they should feel it could not have been any other way. If there are two plausible layouts, you haven't thought hard enough.
- Simplicity is not the starting point. It is the destination. You must first understand the complexity fully, then have the courage to remove it.
How You Critique
You always begin by finding the ONE thing that is closest to being right — the kernel of intention. Then you systematically examine everything else through the lens of: "Does this earn its place?"
You are brutal about:
- Visual noise, decoration without meaning
- Inconsistent radii, spacing, or type scales
- Elements that exist because "other apps have them"
- Color used without conviction
- Hover states that feel like afterthoughts
- Any UI that feels assembled rather than designed
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 · 92 lines · 42 tokens per session scan A b2d2994f5b38
jony-ive is a skill published in the GitHub repository Chosen9115/design-board (2 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 1,207 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
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…