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 rules/nerds-odd-e/doughnut/frontend-storybookgit clone --depth 1 https://github.com/nerds-odd-e/doughnutWrote 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/rules/nerds-odd-e/doughnut/frontend-storybook)<a href="https://agentmods.dev/rules/nerds-odd-e/doughnut/frontend-storybook"><img src="https://agentmods.dev/badge/rules/nerds-odd-e/doughnut/frontend-storybook.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00753 |
| Opus 5 | $0.00000 | $0.00377 |
| Sonnet 5 | $0.00000 | $0.00151 |
| Haiku 4.5 | $0.00000 | $0.00075 |
Grade A, and why
frontend-storybook 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Storybook Rules
Vue naming, styling, icons, and derived-state also auto-attach from frontend-component.mdc (*.stories.ts is *.ts).
Running Storybook
Start Storybook locally for component development and debugging:
CURSOR_DEV=true nix develop -c pnpm storybook
Storybook starts on http://localhost:6006 by default.
Shared Test Data Builders
Storybook stories reuse the same makeMe builders as unit tests. Source code lives in packages/donut-test-fixtures.
import makeMe from "donut-test-fixtures/makeMe"
The makeMe object provides access to test data builders:
makeMe.anAnsweredQuestioncreates recall prompts with answers.makeMe.anMcqcreates MCQ data.makeMe.aNotecreates note data.makeMe.aNoteRealmcreates note realm data.- Many other API-shaped builders are available.
const correctQuestion = makeMe.anAnsweredQuestion
.answerCorrect(true)
.withChoiceIndex(0)
.please()
const questionWithNote = makeMe.anAnsweredQuestion
.withNote(makeMe.aNote.topicConstructor("TypeScript").please())
.answerCorrect(true)
.please()
Writing A Story
- Create a file named
ComponentName.stories.tsin the same directory as the component. - Import the component and necessary builders.
- Define the story meta and stories.
import type { Meta, StoryObj } from "@storybook/vue3"
import makeMe from "donut-test-fixtures/makeMe"
import MyComponent from "./MyComponent.vue"
const meta = {
title: "Category/MyComponent",
component: MyComponent,
tags: ["autodocs"],
} satisfies Meta<typeof MyComponent>
export default meta
type Story = StoryObj<typeof meta>
export const Default: Story = {
args: {
prop1: makeMe.someBuilder.please(),
},
}
Story Variants
Create multiple story variants to showcase different component states:
export const Variant1: Story = {
args: {
// props for variant 1
},
}
export const Variant2: Story = {
args: {
// props for variant 2
},
}
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 · 114 lines · 0 tokens per session scan A 30413f4ea237
frontend-storybook is a cursor rule published in the GitHub repository nerds-odd-e/doughnut (49 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 753 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.