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/review-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/review-storybook)<a href="https://agentmods.dev/skills/paperclipai/paperclip/review-storybook"><img src="https://agentmods.dev/badge/skills/paperclipai/paperclip/review-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/review-storybook"><img src="https://agentmods.dev/badge/skills/paperclipai/paperclip/review-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.00655 |
| Opus 5.5 | $0.00016 | $0.00262 |
| Sonnet 5.5 | $0.00008 | $0.00131 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
review-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.
What it actually says
Review Storybook
Read the catalog contract and find the
requested capability in its generated index. Check the relevant feature recipe,
production subject, and story before driving it. Catalog status is prior review
context, not proof of the current revision. This skill consumes the maps/catalog;
corrections belong to maintain-storybook or maintain-verification-skill.
Choose discriminating states for the requested change: the normal action and result, relevant failure/retry, gate/permission presentation, and mobile/theme variants where affected. Record chosen files/exports and omitted scope. For a full source review, account for every file; do not describe sampling as full render or interaction coverage.
When reviewing navigation/index changes, compare the guide and sidebar with the full ordered index generated from feature recipes' navigation metadata. Open a feature without examples and a feature whose related suite lives elsewhere; check capability order, gap messages, classifications, recipe links, and actual suite navigation. Compare built entry IDs before/after so existing links survive. Generated Overview pages do not establish new example coverage.
Use the existing Storybook commands:
pnpm build-storybook, or an owned Storybook dev server on an available local
port. Use the built ui/storybook-static/index.json for actual story IDs and
links. Do not trust an unrelated server on the default port. Keep the process
handle and stop only the server this review started, retaining useful evidence.
Inspect the real rendered subject, including errors and browser console output.
For interactive stories, wait for their play assertions to complete and inspect
the observable result. A screenshot alone does not prove play passed. Verify
fixture isolation by revisiting/resetting relevant stories when they mutate
fetch handlers, storage, query caches, time, or module state. Avoid real provider
actions; explicitly document any live dependency required by a story.
The existing visual suite is
tests/storybook-visual/storybook-visual.spec.ts. It uses external baselines and
a pinned Linux environment. Inspect baseline-manifest.json before claiming
visual regression proof. An unpublished manifest blocks comparisons; a macOS
capture is useful inspection, not the Linux baseline. Do not update/publish
baselines just to make a review pass. Use existing focused browser suites where
they cover the requested scenario, and the production verification skill when
the question requires backend persistence, real authorization, or provider proof.
Report each selected case as passed, failed, blocked, or not run, naming revision, story ID, environment, production versus prototype subject, simulated boundaries, action/assertion and observed result. Separate render, interaction, visual comparison, and production acceptance evidence. Report proven drift with exact source references and a proposed correction; do not lower expectations, remove failing cases, or silently bless historical behavior as current.
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 · +7 lines 17b8db7d9696
- 12d ago First seen · 48 lines · 39 tokens per session scan A 7dcbbd991109
review-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 655 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
agent-production-validator
Agent skill for production-validator - invoke with $agent-production-validator.
agent-tester
Agent skill for tester - invoke with $agent-tester.
test-automation
Execute Vitest and Playwright test suites with result collection and failure analysis.
qa-testing
Generate and execute API and E2E tests with quality gate assessment.
run-dashboard-e2e-local-changes
Run Playwright E2E (tests/e2e/) against the docker/ all-in-one harness so it reflects LOCAL code changes, not a stale cached image.
acceptance-criteria-gwt
Use when writing acceptance criteria for a task - express each as an observable Given/When/Then that QA can execute, including negative cases.