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 agentmods add skills/aziontech/webkit/storybook-writenpx skills add aziontech/webkit --skill storybook-writegit clone --depth 1 https://github.com/aziontech/webkitWhat 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 | $0.00156 | $0.05644 |
| Opus 5 | $0.00078 | $0.02822 |
| Sonnet 5 | $0.00031 | $0.01129 |
| Haiku 4.5 | $0.00016 | $0.00564 |
Grade A, and why
storybook-write 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 2d 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 — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: storybook-write
Purpose
Generate apps/storybook/src/stories/components/<category>/<name>/<PascalName>.stories.js (or apps/storybook/src/stories/components/<category>/<PascalName>.stories.js for short-form locations) covering only the stories listed in the spec's "Stories (Storybook)" section. The canonical shape is the existing Button.stories.js — composite Types and Sizes stories plus state-specific stories (Loading, Disabled).
"Show code" copy-paste-ready (canonical). parameters.docs.description.component carries a short prose lead (the ## Purpose paragraph) — NOT the spec's ## Usage code block. The runnable usage is surfaced by the Docs "Show code" panel via an explicit source.code on every story, built with toSfc from apps/storybook/src/stories/_shared/story-source.js:
- Keep
parameters.docsa plain object literal (a helper call there makes Storybook print the raw CSF story object). Setdescription.component(prose lead) andcanvas.sourceState: 'shown'at the meta level. - Give every story
parameters.docs.source.code: toSfc(IMPORT, TEMPLATE). For composite / state stories, define the markup as aconst, render it, and pass the same const totoSfc(zero drift). For the arg-drivenDefault, keeprender: Templateand setsource.codeto the canonical default markup.
Do NOT use Storybook's dynamic source (source.transform / source.type: 'dynamic') — it lowercases tags (<skeleton>, <chips>), double-wraps <template>, and falls back to the raw story object. The snippet MUST be a single runnable SFC whose tags match the import (PascalCase). Enforced by validate-story-source.mjs. Full rule: .claude/rules/storybook-source.md. (Reference: Skeleton.stories.js.)
When to invoke
- Step 5 of
/component-create, after the scaffolder succeeded.
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.
- 2d ago First seen · 322 lines · 0 tokens per session scan A f48b41bfc547
storybook-write is a skill published in the GitHub repository aziontech/webkit (2 stars, last pushed 5d ago), licensed MIT. It adds 156 tokens to every session and 5,644 once invoked, about $0.0008 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
monorepo-management
Sets up or audits a monorepo workspace: tool selection, package naming, shared tooling, inter-package dependencies, selective CI, and versioning strategy. Invoked when the user asks to set up a monorepo, add a workspace, or manage multiple packages in a single repository.
bazel-monorepo-expert
Expert knowledge for managing large-scale Bazel monorepos with multiple services, shared libraries, and cross-cutting concerns. Use for workspace structure, visibility, and dependency management.
pnpm
Skill "pnpm" from pledgeandgrow/pledge-skills, covering pnpm documentation skill, key benefits, file index, quick start and install pnpm.
fast-typescript-check
Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…
port-sacred-terminal-ui-to-react-using-same-conventions
Take a CLI screen written for Simulacrum — the sacred CLI framework (scripts/cli/templates/.ts or scripts/python/templates/.py) — and produce a React component that lives inside components/examples/ (or components/) using only sacred's existing primitives — Window, Card, SimpleTable, ActionButton, RowSpaceBetween…
tinyvue-develop-spec
在当前仓库进行组件的开发，主题开发，国际化开发，测试脚本开发时，必须遵守以下规范。.