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/release/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/release)<a href="https://agentmods.dev/skills/paperclipai/paperclip/release"><img src="https://agentmods.dev/badge/skills/paperclipai/paperclip/release/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/release"><img src="https://agentmods.dev/badge/skills/paperclipai/paperclip/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 37 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00041 | $0.02337 |
| Opus 5.5 | $0.00016 | $0.00935 |
| Sonnet 5.5 | $0.00008 | $0.00467 |
| Haiku 4.5 | $0.00004 | $0.00234 |
Grade A, and why
release 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- release — 86% identical, 76 lines differ
How it starts
The opening of the file, as written. The whole thing — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Coordination Skill
Run the full Paperclip maintainer release workflow, not just an npm publish.
This skill coordinates:
- stable changelog drafting via
release-changelog - canary verification and publish status from
master - Docker smoke testing via
scripts/docker-onboard-smoke.sh - manual stable promotion from a chosen source ref
- GitHub Release creation
- website / announcement follow-up tasks
- release-content Cases dogfood: a top-level
releasecase with childblog_postandtweet_stormcases, all linked to the release issue/run
Trigger
Use this skill when leadership asks for:
- "do a release"
- "ship the release"
- "promote this canary to stable"
- "cut the stable release"
Preconditions
Before proceeding, verify all of the following:
.agents/skills/release-changelog/SKILL.mdexists and is usable.- The repo working tree is clean, including untracked files.
- There is at least one canary or candidate commit since the last stable tag.
- The candidate SHA has passed the verification gate or is about to.
- If manifests changed, the CI-owned
pnpm-lock.yamlrefresh is already merged onmaster. - npm publish rights are available through GitHub trusted publishing, or through local npm auth for emergency/manual use.
- If running through Paperclip, you have issue context for status updates and follow-up task creation.
If any precondition fails, stop and report the blocker.
Inputs
Collect these inputs up front:
- whether the target is a canary check or a stable promotion
- the candidate
source_reffor stable - whether the stable run is dry-run or live
- release issue / company context for website and announcement follow-up
Step 0 — Release Model
Paperclip now uses a commit-driven release model:
- every push to
masterpublishes a canary automatically - canaries use
YYYY.MDD.P-canary.N - stable releases use
YYYY.MDD.P - the middle slot is
MDD, whereMis the UTC month andDDis the zero-padded UTC day - the stable patch slot increments when more than one stable ships on the same UTC date
- stable releases are manually promoted from a chosen tested commit or canary source commit
- only stable releases get
releases/vYYYY.MDD.P.md, git tagvYYYY.MDD.P, and a GitHub Release
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 · 324 lines · 41 tokens per session scan A 49ad05341846
release is a skill published in the GitHub repository paperclipai/paperclip (107,044 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 2,337 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
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
publish-harness
Publish a generated harness to npm — runs the smoke test, signs the witness manifest, and dispatches npm publish --provenance from your tagged release.
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.