Borrowing it
Nothing to install: this file belongs to leboncoin/spark-web. 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/leboncoin/spark-web/main/.cursor/skills/chrome-devtools-storybook/SKILL.mdgit clone --depth 1 https://github.com/leboncoin/spark-webWrote 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/leboncoin/spark-web/chrome-devtools-storybook)<a href="https://agentmods.dev/skills/leboncoin/spark-web/chrome-devtools-storybook"><img src="https://agentmods.dev/badge/skills/leboncoin/spark-web/chrome-devtools-storybook/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/leboncoin/spark-web/chrome-devtools-storybook"><img src="https://agentmods.dev/badge/skills/leboncoin/spark-web/chrome-devtools-storybook.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00038 | $0.01064 |
| Opus 5 | $0.00019 | $0.00532 |
| Sonnet 5 | $0.00008 | $0.00213 |
| Haiku 4.5 | $0.00004 | $0.00106 |
Grade A, and why
chrome-devtools-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 5d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chrome DevTools + Storybook Browser Tests
Use the project-0-spark-chrome-devtools MCP server to run browser-level tests and interactions against local Storybook stories. Storybook renders stories inside iframes on the docs pages, so you must always target the underlying iframe.html story URL to avoid unnecessary DOM exploration.
When to Use
- User asks for browser-based testing or visual checks of a Storybook component
- User mentions chrome devtools, CDP, DevTools MCP, or similar
- User provides a Storybook URL on
http://localhost:6006(or another Storybook host) - You need to interact with a specific story (click, type, focus, keyboard navigation, screenshots, etc.)
Storybook URL Rules
Storybook has two kinds of URLs:
- Docs pages (outer shell with iframes and MDX):
http://localhost:6006/?path=/docs/components-accordion--docs - Story iframes (what you actually want to test):
http://localhost:6006/iframe.html?id=components-accordion--default&viewMode=story
Always navigate chrome-devtools to the iframe URL, not the docs page.
Converting docs/story URLs to iframe URLs
-
Docs page URL (
?path=/docs/...):- Example:
http://localhost:6006/?path=/docs/components-accordion--docs - Extract the part after
/docs/and before--docs→ here:components-accordion - Build the default story id by appending
--default:id=components-accordion--default
- Final iframe URL:
http://localhost:6006/iframe.html?id=components-accordion--default&viewMode=story
- Example:
-
Story page URL (
?path=/story/...):- Example:
http://localhost:6006/?path=/story/components-accordion--with-icon - Extract everything after
/story/→ here:components-accordion--with-icon - Use this as the
iddirectly:id=components-accordion--with-icon
- Final iframe URL:
http://localhost:6006/iframe.html?id=components-accordion--with-icon&viewMode=story
- Example:
-
Other query params:
- Always include
viewMode=storyin the iframe URL. - If the user provides
globals,args, or other query parameters, append them to the iframe URL as-is.
- Always include
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.
- 5d ago First seen · 83 lines · 38 tokens per session scan A 1634d377bec0
chrome-devtools-storybook is a skill published in the GitHub repository leboncoin/spark-web (93 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 1,064 once invoked, about $0.0002 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-09-05.
Other skills, from other repositories
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
verify
Build/launch/drive recipe for verifying apps/docs changes at runtime (demos, docs pages, llms.txt).
storybook-mcp-integration
Reference for the Storybook MCP server itself (@storybook/addon-mcp): 6 tools across 3 toolsets (dev, docs, testing), availability detection, and per-agent toolset filtering. Use when setting up the server or calling these tools directly against components that already exist. For the end-to-end pipeline that turns a…
webapp-testing
Web application testing principles. E2E, Playwright, deep audit strategies.
sigil-audit
The auditor crawls every /docs/components/ page on the local dev server and combines static MDX analysis with a real Chromium browser pass.
test-component
Runs, analyzes, and fixes Playwright and accessibility tests for a specific DB UX component.