Paperclip is a Node.js server and React application for coordinating AI agents as a business team, with goals, organizational roles, budgets, governance, and work tracking in one interface. It is used by people managing multiple agents or autonomous agent organizations across tools such as OpenClaw, Claude Code, Codex, and Cursor. The catalogue includes skills, agents, an MCP add-on, and an instruction for working with Paperclip.
Borrowing it
Nothing to install: this file belongs to paperclipai/paperclip. 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/paperclipai/paperclip/master/.agents/skills/maintain-storybook/SKILL.mdgit clone --depth 1 https://github.com/paperclipai/paperclipWrote 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/paperclipai/paperclip/maintain-storybook)<a href="https://agentmods.dev/skills/paperclipai/paperclip/maintain-storybook"><img src="https://agentmods.dev/badge/skills/paperclipai/paperclip/maintain-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/paperclipai/paperclip/maintain-storybook"><img src="https://agentmods.dev/badge/skills/paperclipai/paperclip/maintain-storybook.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.00039 | $0.01270 |
| Opus 5.5 | $0.00016 | $0.00508 |
| Sonnet 5.5 | $0.00008 | $0.00254 |
| Haiku 4.5 | $0.00004 | $0.00127 |
Grade A, and why
maintain-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 11d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintain Storybook
Read the Storybook catalog contract,
the relevant feature recipes, and
DESIGN.md. The feature map is an upstream input. This skill
owns stories, their fixtures/support, and maps/storybook-map/; it does not edit
the feature or agent-access maps. Report upstream drift to
maintain-verification-skill with source evidence.
Reconcile the requested scope
For a feature/change, follow its capability IDs to catalog entries and shared
dependencies. For a full inventory, account for every configured story file,
including historical examples. Start with node scripts/storybook-catalog.mjs.
Record the source revision and whether the pass covers source, rendering,
interactions, or visual comparisons. Inventory completeness is not behavioral
coverage. Do not expand a targeted maintenance request into an all-product audit.
Compare each affected story's rendered subject, props, fixture responses, actions, and assertions with the production implementation and recipe. Follow imported wrappers: a production Button inside a locally recreated page does not make that page a production-component story. A real production page using mocked APIs is valid isolation; record component provenance and data simulation separately. Inspect mock methods/paths, payload shapes, errors, identity, gates, and reset behavior. An API method returning success without the relevant state transition can hide drift. Do not replace errors with generic successful mocks to pass.
Prefer mounting the shipped subject and mocking its external boundary. Retain local layout wrappers and fixture data when they serve that isolation. Replace a duplicate product implementation only when the current component expresses the same scenario without losing the original purpose. Production bugs and larger redesigns are separate findings, not reasons to rewrite expected behavior.
Classify current examples, proposals, historical explorations, and unresolved
cases explicitly. Use unreviewed when evidence does not establish parity.
Retain useful superseded work with its rationale and replacement reference;
do not delete a story merely because it is old, mocked, or duplicated by name.
Record mixed suites honestly and split them only when that improves review.
What ships with it
1 file 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.
- 11d ago Changed · +26 lines 66d685b88d28
- 12d ago First seen · 79 lines · 39 tokens per session scan A 270ef82177ba
maintain-storybook is a skill published in the GitHub repository paperclipai/paperclip (107,044 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 1,270 once invoked, about $0.0002 per session on Opus 5.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-10-13.
Other skills, from other repositories
deep-reasoning
Structured multi-step reasoning tool for complex problem solving with branching, hypothesis testing, and evidence tracking.
agent-benchmark-suite
Agent skill for benchmark-suite - invoke with $agent-benchmark-suite.
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
agent-production-validator
Agent skill for production-validator - invoke with $agent-production-validator.
agent-tester
Agent skill for tester - invoke with $agent-tester.
agent-implementer-sparc-coder
Agent skill for implementer-sparc-coder - invoke with $agent-implementer-sparc-coder.