Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/PMDevSolutions/Aureliusnpx agentmods add skills/pmdevsolutions/aurelius/storybook-story-generationWrote 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/pmdevsolutions/aurelius/storybook-story-generation)<a href="https://agentmods.dev/skills/pmdevsolutions/aurelius/storybook-story-generation"><img src="https://agentmods.dev/badge/skills/pmdevsolutions/aurelius/storybook-story-generation/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/pmdevsolutions/aurelius/storybook-story-generation"><img src="https://agentmods.dev/badge/skills/pmdevsolutions/aurelius/storybook-story-generation.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.00115 | $0.02514 |
| Opus 5 | $0.00057 | $0.01257 |
| Sonnet 5 | $0.00023 | $0.00503 |
| Haiku 4.5 | $0.00012 | $0.00251 |
Grade A, and why
storybook-story-generation 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 4d 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Storybook Story Generation — AST-Based Stories + MDX Docs
Purpose
Auto-generate Storybook 8 (CSF3) stories and MDX documentation from built React
components. The generator parses each component's TypeScript source with a
ts-morph AST — not regex — so it can reliably extract prop types, string-literal
unions, default values, callback props, and JSDoc comments, then emit:
Component.stories.tsx—Metawithtags: ['autodocs'], prop-awareargTypes/controls, aDefaultstory seeded with destructured defaults, one variant story per union value,True/Falsestories for booleans, action args for callbacks, and optional responsive-viewport stories.Component.mdx— an autodocs page withMeta,Canvas,Controls, andArgTypesblocks, plus the component's JSDoc description and aCanvasper variant.
The skill wraps scripts/generate-stories.sh (a thin wrapper over
scripts/generate-stories.js). It is a non-blocking step: a failure never
fails the build.
When to Use
- Phase 4.5 of
/build-from-figma,/build-from-canva, and/build-from-screenshot— immediately after components are built and unit tests pass, before/alongside visual QA (runs in parallel, non-blocking). - Backfilling Storybook coverage for an existing component library.
- When the user asks to "generate Storybook stories", "add stories for these components", "create autodocs", or "document components in Storybook".
Trigger phrases:
- "Generate Storybook stories"
- "Auto-generate stories for my components"
- "Add MDX docs to Storybook"
- "Create stories with controls and variants"
Do NOT use for: hand-authored interaction/play() tests (those belong to the
react-testing-workflows skill), or non-React output targets.
Inputs
- Required: Built components under
src/components/**/*.tsx(override with--src-dir). Components must be exported and named with an uppercase first letter (function, arrow-const, or default export). - Recommended: A props
interface ComponentNameProps— the generator keys off this naming convention to build controls and variants. - Optional:
.claude/pipeline.config.json→storybook(thresholds and toggles; see Configuration). - Optional:
tsconfig.json— used byts-morphwhen present; otherwise a sensible in-memory compiler config is used.
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.
- 4d ago First seen · 223 lines · 0 tokens per session scan A 6092f0cee036
storybook-story-generation is a skill published in the GitHub repository PMDevSolutions/Aurelius (8 stars, last pushed 24d ago), licensed MIT. It adds 115 tokens to every session and 2,514 once invoked, about $0.0006 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-09-04.
Other skills, from other repositories
frontend-code-review
Trigger when the user requests a review of frontend files (e.g., .tsx, .ts, .js). Support both pending-change reviews and focused file reviews while applying the checklist rules.
figma-codegen
Generate framework-aware code from a Figma design. Reads the project's stack profile and emits code matching the existing framework (React/Vue/Svelte/Next/etc.) and styling (Tailwind/CSS/CSS-in-JS), reusing existing components and design tokens instead of regenerating from scratch. Triggers whenever the user wants a…
ag-auditar-react-hooks
Auditor de Hooks React. Detecta violacoes das Rules of Hooks, deps faltando/excessivas em useEffect/useMemo/useCallback, candidatos a custom hook, useState que deveria virar useReducer. Use para audit qualidade React proativo.
ag-referencia-nextjs
Patterns e convencoes para projetos Next.js com React.
frontend-dataviz
A skill for choosing and creating clear charts from user-provided data, following the Storytelling with Data approach. It matches chart types to tasks such as comparing categories, showing trends, or displaying distributions.
mk:figma
Read-first Figma gateway via Figma MCP: analyze designs, implement Figma-to-code for 1–3 screens, extract design tokens, produce a Figma Evidence Packet for planning handoff, screenshot fallback. Advanced operations (Code Connect, canvas writes, design-system/library patterns) are gated references loaded only on…