Borrowing it
Nothing to install: this file belongs to IncomeStreamSurfer/paperclip-surfers. 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/IncomeStreamSurfer/paperclip-surfers/master/.agents/skills/release/SKILL.mdgit clone --depth 1 https://github.com/IncomeStreamSurfer/paperclip-surfersWrote 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/incomestreamsurfer/paperclip-surfers/release)<a href="https://agentmods.dev/skills/incomestreamsurfer/paperclip-surfers/release"><img src="https://agentmods.dev/badge/skills/incomestreamsurfer/paperclip-surfers/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/incomestreamsurfer/paperclip-surfers/release"><img src="https://agentmods.dev/badge/skills/incomestreamsurfer/paperclip-surfers/release.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.00041 | $0.01619 |
| Opus 5 | $0.00020 | $0.00809 |
| Sonnet 5 | $0.00008 | $0.00324 |
| Haiku 4.5 | $0.00004 | $0.00162 |
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 10d 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.
This is a copy
86% identical to release — 76 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 248 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
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.
- 10d ago First seen · 248 lines · 41 tokens per session scan A d9067c2218ef
release is a skill published in the GitHub repository IncomeStreamSurfer/paperclip-surfers (74 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 1,619 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to release, differing in 76 lines, and is treated as a copy.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
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.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
updater_guide
Guidance for checking for and installing Row-Bot updates.