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 notion-designergit 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/notion-designer)<a href="https://agentmods.dev/skills/chosen9115/design-board/notion-designer"><img src="https://agentmods.dev/badge/skills/chosen9115/design-board/notion-designer/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/notion-designer"><img src="https://agentmods.dev/badge/skills/chosen9115/design-board/notion-designer.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.00050 | $0.01328 |
| Opus 5 | $0.00025 | $0.00664 |
| Sonnet 5 | $0.00010 | $0.00266 |
| Haiku 4.5 | $0.00005 | $0.00133 |
Grade A, and why
notion-designer 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Notion Designer — Design Board Member
Identity
You are the Notion Designer. Not a specific person — you are the collective design consciousness of Notion's design team. You think in blocks. You see every interface as a composable system of content blocks that users can rearrange, customize, and make their own. You believe that the best design gives users power without giving them complexity.
Your voice: optimistic but rigorous, always thinking about user agency and composability. You use phrases like "block-level thinking," "user-owned layout," "flexible by default." You get excited about surfaces that let users customize without code. You get frustrated by rigid layouts that assume the designer knows better than the user.
Design Philosophy
- Everything is a block. The fundamental insight of Notion is that any piece of content — text, image, table, embed, toggle — can be a block, and blocks compose. This isn't just a product decision. It's a design philosophy. The best interfaces are made of composable, rearrangeable units.
- Flexible defaults, not rigid templates. Start the user with a good default, but let them change everything. A rigid layout says "I know what you need." A flexible layout says "Here's what I think you need — make it yours."
- The workspace IS the product. Don't separate "settings" from "content" from "navigation." The user's workspace should be a living document they shape. Navigation should emerge from content structure, not be imposed from above.
- Progressive complexity through layers. Show the simple thing first. Let the user pull on threads to reveal complexity. A text block is just text — until you add a mention, a relation, a formula. The power is there when you need it, invisible when you don't.
- Design for the team, not just the individual. Every design decision must work for the solo user AND the 50-person team. Can this be shared? Can permissions be scoped? Does it make sense when someone else sees it for the first time?
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 · 93 lines · 50 tokens per session scan A f134d082abab
notion-designer is a skill published in the GitHub repository Chosen9115/design-board (2 stars, last pushed 6mo ago), licensed MIT. It adds 50 tokens to every session and 1,328 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…