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/prepare-paperclip-pr/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/prepare-paperclip-pr)<a href="https://agentmods.dev/skills/paperclipai/paperclip/prepare-paperclip-pr"><img src="https://agentmods.dev/badge/skills/paperclipai/paperclip/prepare-paperclip-pr/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/prepare-paperclip-pr"><img src="https://agentmods.dev/badge/skills/paperclipai/paperclip/prepare-paperclip-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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.00021 | $0.00983 |
| Opus 5 | $0.00010 | $0.00491 |
| Sonnet 5 | $0.00004 | $0.00197 |
| Haiku 4.5 | $0.00002 | $0.00098 |
Grade A, and why
prepare-paperclip-pr 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare Paperclip PR
The standard Paperclip procedure for turning branch work into a reviewed,
green pull request against paperclipai/paperclip master. Apply it once per
PR (if a task splits a branch into several PRs, run the whole procedure for
each one).
0. Preconditions — worktree safety
- Do all PR work in a git worktree on a dedicated branch. The main
~/paperclipcheckout typically runs the live Paperclip server — never check out branches there. If you are already on a worktree/branch, verify it (git rev-parse --git-dir,git branch --show-current) and proceed. - If the main checkout is unexpectedly off
master, fix that first without losing work (usually: move that branch's work into a worktree). - Confirm which remote/ref you are targeting (normally
masteron thepaperclipai/papercliprepo; the task may name a specific remote such asoriginorpublic-gh).
1. Commit everything — lose no work
- Make logical commits of all uncommitted changes before anything else. Do not stash and forget; do not leave files behind. If commits are missing, make them.
- Commit messages must end with exactly:
Co-Authored-By: Paperclip <[email protected]>
2. Get changes cleanly on top of master
- Fetch the target remote and rebase (or otherwise replay) your branch on top of the target master so the PR has no merge conflicts.
- Re-verify after rebase: build/tests relevant to the change still pass at whatever depth the task warrants.
3. Guardrails checklist (every PR)
- Never commit
pnpm-lock.yaml— the repo has actions that manage it. If it is already in a commit, rewrite/drop that change before pushing. - Never change
.github/workflows/*unless the underlying commit was explicitly about that and the task calls it out. - No design screenshots / wireframe images committed to the repo unless they are genuinely part of the work product.
- Migrations: numbered incrementally with no conflicts against master. If master moved and took your number, renumber on top. Make migrations idempotent so users who already applied the old number are safe.
- Greptile file limit: keep each PR under 100 changed files; if a PR exceeds that, split it into two.
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 First seen · 86 lines · 21 tokens per session scan A 61e9ff0adcf8
prepare-paperclip-pr is a skill published in the GitHub repository paperclipai/paperclip (80,385 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 983 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".