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/paperclip-create-plugin/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/paperclip-create-plugin)<a href="https://agentmods.dev/skills/paperclipai/paperclip/paperclip-create-plugin"><img src="https://agentmods.dev/badge/skills/paperclipai/paperclip/paperclip-create-plugin/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/paperclip-create-plugin"><img src="https://agentmods.dev/badge/skills/paperclipai/paperclip/paperclip-create-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00045 | $0.01530 |
| Opus 5.5 | $0.00018 | $0.00612 |
| Sonnet 5.5 | $0.00009 | $0.00306 |
| Haiku 4.5 | $0.00005 | $0.00153 |
Grade A, and why
paperclip-create-plugin 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 1mo 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create and develop a Paperclip plugin
Use this skill when the task is to create, scaffold, or iterate on a Paperclip plugin against a local Paperclip instance.
1. Default: build the plugin OUTSIDE Paperclip core
Plugins are their own packages. Unless the task explicitly asks for a bundled in-repo example, do not add plugin source under packages/plugins/ in this repo.
- Scaffold the plugin into a directory outside the Paperclip checkout (e.g.
~/dev/paperclip-plugins/<name>). - Install it into the running Paperclip instance by local absolute path.
- Edit code in the external package; let Paperclip pick up rebuilt output.
Only edit Paperclip core itself when the user asks to surface a plugin as a bundled example (server/src/routes/plugins.ts, in-repo example lists, docs).
2. Ground rules
Reference docs when you need detail:
doc/plugins/PLUGIN_AUTHORING_GUIDE.mdpackages/plugins/sdk/README.mddoc/plugins/PLUGIN_SPEC.md— future-looking context only
Current runtime assumptions:
- plugin workers are trusted code
- plugin UI is trusted same-origin host code
- worker APIs are capability-gated
- plugin UI is not sandboxed by manifest capabilities
- no host-provided shared plugin UI component kit yet
ctx.assetsis not supported in the current runtime
3. CLI-first scaffold workflow
Use paperclipai plugin init. Do not invoke the scaffold package node entrypoint by hand unless the CLI command is unavailable in the environment.
paperclipai plugin init @acme/my-plugin --output ~/dev/paperclip-plugins
Useful flags (all optional):
--output <dir>— parent directory; the command creates<dir>/<unscoped-name>/. Defaults to the current directory.--template <default|connector|workspace|environment>— starter template.--category <connector|workspace|automation|ui|environment>— manifest category.--display-name <name>,--description <text>,--author <name>— manifest metadata.--sdk-path <path>— snapshot the local SDK from a Paperclip checkout into.paperclip-sdk/(useful when developing against an unreleased SDK).
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.
- 1mo ago First seen · 153 lines · 45 tokens per session scan A 6318d09f9d3a
paperclip-create-plugin is a skill published in the GitHub repository paperclipai/paperclip (107,044 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 1,530 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-08-30.
Other skills, from other repositories
fleetq-connect
Connect an agent to FleetQ over MCP or the REST API, including obtaining credentials via dynamic client registration.
fleetq-manage-workflow
Build, validate, cost, and execute FleetQ visual DAG workflows — including generating one from a natural-language goal.
fleetq-run-experiment
Create, run, monitor, and recover a FleetQ experiment through its 20-state pipeline via MCP tools or the REST API.
atelier
Operate the Atelier software factory (the ADW engine stamped into this repo's adws/). Use when the user says /atelier, wants to create / run / update an ADW or workflow, manage the agent roster in sssf.config.yaml, keep the engine current, or observe running agent workflows. Keywords - atelier, software factory, ADW…
deep-reasoning
Structured multi-step reasoning tool for complex problem solving with branching, hypothesis testing, and evidence tracking.
app-launcher
Launch applications, open URLs in browser, and list running processes. Requires approval for launching applications.