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 armelhbobdad/oh-my-skills --skill oms-storybook-react-vitegit clone --depth 1 https://github.com/armelhbobdad/oh-my-skillsWrote 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/armelhbobdad/oh-my-skills/oms-storybook-react-vite)<a href="https://agentmods.dev/skills/armelhbobdad/oh-my-skills/oms-storybook-react-vite"><img src="https://agentmods.dev/badge/skills/armelhbobdad/oh-my-skills/oms-storybook-react-vite/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/armelhbobdad/oh-my-skills/oms-storybook-react-vite"><img src="https://agentmods.dev/badge/skills/armelhbobdad/oh-my-skills/oms-storybook-react-vite.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.00236 | $0.03440 |
| Opus 5 | $0.00118 | $0.01720 |
| Sonnet 5 | $0.00047 | $0.00688 |
| Haiku 4.5 | $0.00024 | $0.00344 |
Grade A, and why
oms-storybook-react-vite 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 12d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Storybook v10 consolidates what used to be ~40 separate @storybook/* packages into a single published storybook package exposing 40 subpath exports (including ./internal/*). This skill grounds Claude in that consolidated import surface so it stops generating outdated @storybook/addon-actions, @storybook/test, @storybook/preview-api imports that training data still shows.
- Scope: day-90+ story author on a Storybook 10.3+ React+Vite project. Not a setup/install guide —
.storybook/main.tsframework pick and addon registration are edited quarterly and covered by the official upgrade CLI. - Packages covered:
storybook(core, 40 subpaths),@storybook/react-vite(framework),@storybook/react(renderer),@storybook/builder-vite(builder),@storybook/addon-{a11y,docs,themes,vitest}. - Layer model:
@storybook/react-vite(framework) composes@storybook/react(renderer) +@storybook/builder-vite(builder). Defects go in the correct layer. - Source:
github.com/storybookjs/storybook@ tagv10.3.5(commite486d382).[AST:code/frameworks/react-vite/src/preset.ts:L1][AST:code/core/package.json:L48]
Quick Start
Preflight — ALWAYS do this first. Before writing any Storybook code, read the user's project state to ground your answer:
cat .storybook/main.ts # installed version, registered addons, framework in use
cat .storybook/preview.ts # parameters, decorators, globalTypes already set
cat package.json | grep -E '"storybook"|"@storybook/' # resolved versions
If the user's storybook dep is <10.0.0, STOP and tell them — CSF3 + v10 imports below will not apply. [EXT:https://storybook.js.org/docs/get-started/frameworks/react-vite/]
Write a CSF3 story (the canonical v10 pattern):
// Button.stories.tsx
import type { Meta, StoryObj } from '@storybook/react-vite';
import { fn, expect } from 'storybook/test';
import { Button } from './Button';
const meta = {
component: Button,
args: { onClick: fn() },
tags: ['autodocs'],
} satisfies Meta<typeof Button>;
export default meta;
type Story = StoryObj<typeof meta>;
export const Primary: Story = {
args: { label: 'Click me', variant: 'primary' },
};
export const Clicked: Story = {
args: { label: 'Click me' },
play: async ({ canvas, userEvent, args }) => {
const button = canvas.getByRole('button', { name: /click me/i });
await userEvent.click(button);
await expect(args.onClick).toHaveBeenCalled();
},
};
What ships with it
8 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.
- 12d ago First seen · 197 lines · 236 tokens per session scan A 0cc343dc0d71
oms-storybook-react-vite is a skill published in the GitHub repository armelhbobdad/oh-my-skills (7 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 236 tokens to every session and 3,440 once invoked, about $0.0012 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
afrexai-react-production
Complete methodology for building production-grade React applications with architecture decisions, component design, state management, performance optimization, testing, and deployment.
testing-react
Stratégie de Tests React 19 + Compiler 1.0. Use when writing tests, reviewing test coverage, or setting up testing.
react
Operate React applications as a named tool: inspect and diagnose React/Vite projects, design component boundaries and state flow, implement accessible responsive UI, and verify behavior with the project's tests. Use when a task explicitly involves React, JSX/TSX, React hooks, React Router, Vite React configuration, or…
security-react
Sécurité React. Use when reviewing security, implementing auth, or hardening code.
state-management
State Management - React Query, Zustand, MMKV. Use when managing application state.
mastermind-frontend-audit
Read-only review of a finished UI change against the codegraph — a component nothing renders, a props contract changed without its callers, a reinvented component, or a raw value where the design system has a token. Use after implementing React or Vue work; triggers "review this UI change", "check the component", or a…