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 martinstofko219/agentic-design-toolkit --skill storybook-docsgit clone --depth 1 https://github.com/martinstofko219/agentic-design-toolkitWrote 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/martinstofko219/agentic-design-toolkit/storybook-docs)<a href="https://agentmods.dev/skills/martinstofko219/agentic-design-toolkit/storybook-docs"><img src="https://agentmods.dev/badge/skills/martinstofko219/agentic-design-toolkit/storybook-docs/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/martinstofko219/agentic-design-toolkit/storybook-docs"><img src="https://agentmods.dev/badge/skills/martinstofko219/agentic-design-toolkit/storybook-docs.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.00177 | $0.03823 |
| Opus 5 | $0.00088 | $0.01912 |
| Sonnet 5 | $0.00035 | $0.00765 |
| Haiku 4.5 | $0.00018 | $0.00382 |
Grade A, and why
storybook-docs 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Produce design-system documentation for Storybook: an MDX Docs page and the Angular stories that the page embeds as live examples. Document how a component is used, how it behaves, and how the design maps to code — not how it is built internally. Anatomy, measurements, redlines, and token-level specs are out of scope; those come from Figma. Write in the voice of a design-system guideline: clear, prescriptive where it should be, and grounded in why, not just what.
These docs serve two audiences at once: people reading Storybook, and AI agents that consume the pages (via the design-system MCP server) to build UI correctly. Write for both — human-readable guideline prose, with symbol names, variant-to-input mappings, and constraints stated explicitly and verbatim so an agent can act on them without guessing. The goals reinforce each other: docs precise enough for an agent are clearer for people too.
Ground every repo fact in the real files
Every "hard fact" — import paths and package names, component class names and selectors, @Input/@Output/method/event names, design-token names, and which variants and states actually exist — must be copied verbatim from real source in the repo, never written from memory or inferred from a naming pattern. The authoritative sources are the *.component.ts (selector, class name, inputs/outputs, methods, events), the public-api.ts / index.ts / ng-package.json (the public export surface and the package/import path), and the token or theme files (real token names). Existing *.stories.ts or docs MDX can show you the project's import style, but verify anything you borrow from them against the component source. Match the project's real conventions rather than introducing your own.
If a hard fact can't be verified from a real source, stop and ask the user rather than inventing it — a guessed import looks right and still breaks the build, and one wrong symbol undermines trust in the whole page. The design-guidance prose (when and how to use the component, do's and don'ts, placement, accessibility) is still yours to write, but it must not describe variants, props, states, or behaviors the component doesn't actually have.
What ships with it
2 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 · 104 lines · 177 tokens per session scan A 8ab68deb5ff5
storybook-docs is a skill published in the GitHub repository martinstofko219/agentic-design-toolkit (1 stars, last pushed 1mo ago), licensed MIT. It adds 177 tokens to every session and 3,823 once invoked, about $0.0009 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
webgl-holographic-foil
A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
html-ppt-taste-brutalist
16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
make-resume
A Chinese-language tool for creating editable HTML resumes that can be changed in a browser and printed to PDF. It uses available resume templates when they are installed and otherwise provides a simpler fallback.