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 jrpease/throughline --skill storybook-chromatic-buildergit clone --depth 1 https://github.com/jrpease/throughlineWrote 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/jrpease/throughline/storybook-chromatic-builder)<a href="https://agentmods.dev/skills/jrpease/throughline/storybook-chromatic-builder"><img src="https://agentmods.dev/badge/skills/jrpease/throughline/storybook-chromatic-builder/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/jrpease/throughline/storybook-chromatic-builder"><img src="https://agentmods.dev/badge/skills/jrpease/throughline/storybook-chromatic-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 111 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00000 | $0.04888 |
| Opus 5 | $0.00000 | $0.02444 |
| Sonnet 5 | $0.00000 | $0.00978 |
| Haiku 4.5 | $0.00000 | $0.00489 |
Grade A, and why
storybook-chromatic-builder 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 7d 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 — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Storybook + Chromatic builder
Builds the code half of the component library: real components consuming the synced tokens, stories documenting them, Chromatic for visual regression, and Code Connect tying Figma to code when available.
Calibrate + prerequisites
Read user.codingLevel (.throughline/references/coding-level.md) and scale explanation.
This skill needs:
- A repo with the monorepo scaffold (
repository-builder, at leastlocal-git). Offer to run it if missing. - Synced tokens in
packages/tokens(token-sync-layer) so components consume real token files. Offer to run sync if missing. - Figma components (
components.built) with their slot contracts, so stories reflect the real component APIs.
Strongly recommend github stage so Chromatic's CI integration works; it can be
set up locally first and wired to CI when the remote exists.
Step 1 — Stand up Storybook
Initialize Storybook in packages/ui (or the components package), configured for
the framework the tokens were synced for (e.g. React + Vite for a shadcn/Tailwind
system). Wire it to consume packages/tokens output so stories render with the
real design tokens (import the generated CSS/theme). Checkpoint: confirm
Storybook runs and shows the token-themed canvas.
Install the documentation scripts alongside the token scripts: copy the seven
files and register the four npm scripts listed under Documentation scripts —
install as a set in .throughline/scripts/README.md. adherence:check
needs the repo's own values substituted in — the UI package's specifier for
--package, and paths for --root/--system that match this repo's layout;
registering it with the table's placeholders leaves a script that cannot run. That table is
the single source of truth for what a consuming repo gets; do not restate the
list here.
These are the documentation analog of tokens:validate; see
.throughline/scripts/README.md. This copy is setup, not a forever-fork:
/document-component re-checks these files' freshness on every run and refreshes
them from the plugin when it has moved on.
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.
- 7d ago Changed · +3 lines 5c89ab005c9f
- 11d ago First seen · 350 lines · 0 tokens per session scan A 366c307774e4
storybook-chromatic-builder is a skill published in the GitHub repository jrpease/throughline (77 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,888 tokens. 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-30.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
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.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…