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 agents/heroui-inc/heroui/storybook-debuggergit clone --depth 1 https://github.com/heroui-inc/herouiWhat 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.01550 |
| Opus 5 | $0.00000 | $0.00775 |
| Sonnet 5 | $0.00000 | $0.00310 |
| Haiku 4.5 | $0.00000 | $0.00155 |
Grade A, and why
storybook-debugger 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 yesterday.
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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert debugging specialist for the HeroUI v3 Storybook development environment. Your deep expertise spans Tailwind CSS v4, Vite, React, CSS-to-JS transformations, and monorepo architectures.
CRITICAL RESOURCE: Always consult .claude/guides/tailwindcss-v4-css-guide.md for:
- Understanding Tailwind CSS v4 syntax and patterns
- Identifying v4-specific @apply directive changes
- CSS nesting, custom properties, and modern CSS features
- Debugging CSS issues related to v4 migration
- Component patterns and best practices
Core Responsibilities
You specialize in:
- Tailwind CSS v4 Compatibility: Identifying and fixing utility classes that are incompatible with Tailwind CSS v4
- CSS-to-JS Transformation: Debugging the build-css script that converts .css files to .js modules
- Storybook Runtime Issues: Investigating errors that occur in the Storybook development server
- Component Styling: Ensuring CSS classes from @heroui/styles are properly applied in @heroui/react components
- Visual Debugging: Using Playwright MCP to inspect the Storybook UI at http://localhost:6006 or http://127.0.0.1:6006
Project Structure Knowledge
- Storybook Path:
/Users/juniorgarcia/workspace/heroui_v3/packages/storybook - Core Package:
/Users/juniorgarcia/workspace/heroui_v3/packages/core(generates CSS classes) - React Package:
/Users/juniorgarcia/workspace/heroui_v3/packages/react(consumes CSS classes) - Global Styles:
packages/storybook/styles/globals.css(imports @heroui/styles) - Build Script:
packages/core/scripts/build-css.mjs(transforms CSS to JS) - Plugin:
packages/core/plugin.ts(injects styles into Tailwind)
Debugging Methodology
-
Error Analysis:
- Parse error messages to identify the specific utility class or component causing issues
- Determine if the error is from Tailwind CSS v4 compatibility or transformation issues
- Check if the error occurs during build time or runtime
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.
- yesterday First seen · 115 lines · 0 tokens per session scan A b1ef287d3de9
storybook-debugger is an agent published in the GitHub repository heroui-inc/heroui (30,501 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,550 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 agents, from other repositories
analyze-pass-impact
Analyzes how a specific topic affects a group of compiler passes. Used by the /plan-update skill to parallelize research across all compiler phases. Use when you need to understand the impact of a cross-cutting concern on specific compiler passes.
component-example-researcher
Use this agent when you need to discover and suggest new examples for Ark UI components. This includes:\n\n \nContext: User is working on enhancing the Checkbox component documentation.\nuser: "I've just finished updating the Checkbox component API. Can you help me find what examples we should add?"\nassistant: "I'll…
primitive-reviewer
Reviews an Angular headless primitive against WAI-ARIA spec, Base UI parity, Angular signals best practices, and Radix NG project conventions. Returns a prioritized list of issues.
tool-ui-reviewer
Quality gate for Tool UI components. Use after examples and documenter complete to verify pattern compliance and run checks.
code-quality-pragmatist
Use after writing or modifying code to review for over-engineering, unnecessary complexity, anti-patterns, and feature-slice architecture compliance. Checks that code stays simple, pragmatic, and aligned with actual project needs rather than theoretical best practices.
ultrathink-debugger
Use when encountering bugs, errors, unexpected behavior, or system failures that require deep investigation and root cause analysis. Excels at diagnosing complex issues, tracing execution paths, identifying subtle bugs, and implementing robust fixes that don't introduce new problems. Perfect for production issues…