agentmods.dev

release

release is a skill for Claude Code, Codex from paperclipai/paperclip. It costs 41 tokens per session (2,337 once invoked), scanned A, original, MIT.

A release workflow for shipping a Paperclip version from engineering checks through npm, GitHub, smoke tests, and follow-up announcements.

In plain words
What is it for?
Use it to publish a stable release, promote a canary release, run Docker smoke tests, create a GitHub Release, and track related website or announcement work.
Why use it?
It keeps the many steps of a release together and checks important conditions before publishing. This reduces the chance of releasing an unverified or incomplete version.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Not installable on its own: it runs a file from its repository that does not travel with it. Clone the repository, or install whatever ships that file. The line is PAPERCLIPAI_VERSION=canary ./scripts/docker-onboard-smoke.sh.

not rated 80k +238 today A scan 41 tokens original MIT
View the source file paperclipai/paperclip paperclip.ing
About the project

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.

paperclipai/paperclip · 80,074 stars · on GitHub · paperclip.ing

Install

Getting it into your agent

There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for release

README.md
[![agentmods](https://agentmods.dev/badge/skills/paperclipai/paperclip/release.svg)](https://agentmods.dev/skills/paperclipai/paperclip/release)
Your own site
<a href="https://agentmods.dev/skills/paperclipai/paperclip/release"><img src="https://agentmods.dev/badge/skills/paperclipai/paperclip/release.svg" alt="Measured on agentmods" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,337 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00041 $0.02337
Opus 5 $0.00020 $0.01169
Sonnet 5 $0.00008 $0.00467
Haiku 4.5 $0.00004 $0.00234

Measured 6d ago against content hash 49ad05341846, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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 6d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • release — 86% identical, 76 lines differ
.agents/skills/release/SKILL.md · 324 lines

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 release case with child blog_post and tweet_storm cases, 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:

  1. .agents/skills/release-changelog/SKILL.md exists and is usable.
  2. The repo working tree is clean, including untracked files.
  3. There is at least one canary or candidate commit since the last stable tag.
  4. The candidate SHA has passed the verification gate or is about to.
  5. If manifests changed, the CI-owned pnpm-lock.yaml refresh is already merged on master.
  6. npm publish rights are available through GitHub trusted publishing, or through local npm auth for emergency/manual use.
  7. 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_ref for 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:

  1. every push to master publishes a canary automatically
  2. canaries use YYYY.MDD.P-canary.N
  3. stable releases use YYYY.MDD.P
  4. the middle slot is MDD, where M is the UTC month and DD is the zero-padded UTC day
  5. the stable patch slot increments when more than one stable ships on the same UTC date
  6. stable releases are manually promoted from a chosen tested commit or canary source commit
  7. only stable releases get releases/vYYYY.MDD.P.md, git tag vYYYY.MDD.P, and a GitHub Release

Read the full file on GitHub · 324 lines

Changes

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.

  1. 6d ago First seen · 324 lines · 41 tokens per session scan A 49ad05341846

Subscribe to this mod's changes

release is a skill published in the GitHub repository paperclipai/paperclip (80,074 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. 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.

DevOps and cloudGit and workflowReleases
Related

Other skills, from other repositories

agent-release-swarm

Agent skill for release-swarm - invoke with $agent-release-swarm.

ruvnet/ruflo · 19 tokens

release

Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.

openai/symphony · 42 tokens

changelog

Create changelog files for important commits in a PR.

pipecat-ai/pipecat · 13 tokens

multi-agent-release-manager

Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.

chromium/chromium · 27 tokens

refresh-arm-sdk-release

WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…

Azure/azure-sdk-for-net · 91 tokens

publish-registry

Publish @agentos-software/ registry packages from AgentOS. Use whenever the user asks to publish or release registry software/agent packages.

rivet-dev/agentos · 32 tokens