Borrowing it
Nothing to install: this file belongs to the-single-gentlemans-club/storybook-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/the-single-gentlemans-club/storybook-mcp/master/CLAUDE.mdgit clone --depth 1 https://github.com/the-single-gentlemans-club/storybook-mcpWrote 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/instructions/the-single-gentlemans-club/storybook-mcp/claude-md)<a href="https://agentmods.dev/instructions/the-single-gentlemans-club/storybook-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/the-single-gentlemans-club/storybook-mcp/claude-md/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/instructions/the-single-gentlemans-club/storybook-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/the-single-gentlemans-club/storybook-mcp/claude-md.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.00312 | $0.00312 |
| Opus 5 | $0.00156 | $0.00156 |
| Sonnet 5 | $0.00062 | $0.00062 |
| Haiku 4.5 | $0.00031 | $0.00031 |
Grade A, and why
storybook-mcp CLAUDE.md 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.
What it actually says
Project Guidelines
I'm a senior frontend engineer specializing in React, React Native, Storybook, UI, and design systems, and I need my code bases clean, components small and broken up, the repo linted and formatted.
The design of the application and components MUST BE rich, color correct, and beautiful.
There should never be any type errors, nor should stale or zombie code be left behind changes to cause errors. ALWAYS DO A CLEANUP.
HIGH PRIORITY:
-
Make 100% sure all of the packages in the package.json are the latest releases while aligning perfectly with all other packages. There should never be issues with versioning. Never. Always add packages to the package.json when importing libraries, and don't let that make a build or ci fail.
-
For every project documentation should be automated, generated and updated as changes are made to code, components, ideas, plans, roadmaps, etc. Please use Mintlify, Docusaurus or Featurebase for all of the docs across the repo. If not yet built, there needs to be a reusable SKILL or MCP of whichever docs solution we decide upon, which will then be used for all future projects moving forward.
-
Clarifying questions and suggestions are important
-
Update the README.md section "What's New in {version}" where "version" is newest and content are changes, updates, etc. Focus on new features and big fixes, otherwise use the lower level changes.
-
Use git bash if bash unavailable
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 · 20 lines · 312 tokens per session scan A e5da1fd1fde8
storybook-mcp CLAUDE.md is an instructions file published in the GitHub repository the-single-gentlemans-club/storybook-mcp (1 stars, last pushed 4mo ago), licensed MIT. It adds 312 tokens to every session, about $0.0016 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 instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).