Borrowing it
Nothing to install: this file belongs to piperbox/piper. 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/piperbox/piper/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/piperbox/piperWrote 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/piperbox/piper/release)<a href="https://agentmods.dev/skills/piperbox/piper/release"><img src="https://agentmods.dev/badge/skills/piperbox/piper/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/piperbox/piper/release"><img src="https://agentmods.dev/badge/skills/piperbox/piper/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.00056 | $0.02329 |
| Opus 5.5 | $0.00022 | $0.00932 |
| Sonnet 5.5 | $0.00011 | $0.00466 |
| Haiku 4.5 | $0.00006 | $0.00233 |
Grade D, and why
release scanned grade D with 3 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
Expected: installer configures apt.piperbox.dev, installs both debs, both versions print the latest stable. (Runs as root in the container, so no sudo is involved.) Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
docker run --rm debian:stable sh -c 'apt-get update -qq && apt-get install -y -qq curl ca-certificates >/dev/null && curl -fsSL https://get.piperbox.dev/install.sh | sh && piper --version && piperd --version' Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://get.piperbox.dev/install.sh \ How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cutting a Piper release
Releases are semver git tags. Pushing a v* tag triggers .github/workflows/release.yml, which runs goreleaser and publishes a GitHub Release. There is nothing else to run — but the tag is irreversible in practice, so the gates below come first.
Pre-1.0 (0.x), breaking changes may land in minor bumps. See CLAUDE.md's compatibility policy.
1. Preconditions
- On
main, clean tree, synced with origin. make verifyclean locally.
2. The gate: green on the exact tip
The release workflow does not re-run e2e. Whatever you tag is what ships, so verify CI + e2e + Code Quality all succeeded on the exact SHA you are about to tag:
TIP=$(git rev-parse main)
gh run list --branch main --limit 25 --json headSha,name,conclusion \
--jq ".[] | select(.headSha==\"$TIP\") | \"\(.name)\t\(.conclusion)\""
Do not use gh run list --commit <sha> — it has returned empty unreliably. Filter on headSha as above.
If a push-event run is missing entirely (GitHub has occasionally fired no push workflows for a squash-merge), tree-equality against a green PR run is an acceptable substitute: confirm git rev-parse <release-commit>^{tree} equals the tree of the PR head that e2e tested.
3. Choose the version
Ask the user rather than assuming — but bring a recommendation.
Minor bump when the release breaks anything a user must act on. Precedents:
v0.5.0— breaking API response shapev0.6.0— new columns on existing tables, so an in-place DB needs replacingv0.8.0— macOS launchd label changed, requiring a manuallaunchctl bootout
Patch only when nothing requires user action. A patch that silently breaks an upgrade path is worse than a minor: the version number is the only signal most users read.
Schema changes are subtler than they look
Both the agent and relay stores apply schema.sql with CREATE TABLE IF NOT EXISTS and there are no migrations anywhere.
- New table → materializes on an existing DB. Additive, no re-enroll.
- New column on an existing table → does not materialize. Needs a fresh DB and re-enrollment.
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 Changed cc19036ebfdb
- 1mo ago Changed · +11 lines b54963e71353
- 1mo ago Changed e89eed8063ea
- 2mo ago First seen · 164 lines · 56 tokens per session scan D c8fadf1bdbd2
release is a skill published in the GitHub repository piperbox/piper (10 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 2,329 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it D with 3 findings (asks for root, downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
github-release-management
GitHub release orchestration — automated versioning, testing, deployment, and rollback. Use when cutting a release, tagging a version, drafting release notes, or coordinating a deploy/rollback workflow.
ci-cd-pipeline-generator
Use this skill when setting up CI/CD from scratch or adding a pipeline config for GitHub Actions, GitLab CI, CircleCI, or Jenkins. Generates multi-stage pipelines, matrix builds, secrets management, caching, environment promotion, canary deploys, and rollback patterns — the YAML for build/test/deploy workflows, Docker…
dokku-deploy
PaaS deployment with Dokku.
conventional-commit
Rules for writing Conventional Commits messages in this project. MUST be invoked every time a commit is created.
cli-local-build
Build and test the Kurtosis CLI from source. Compile the CLI binary locally, run it against Docker or Kubernetes engines, and iterate on CLI changes without creating a release. Use when developing or debugging CLI commands.
dev-architecture-playbook
Route full software-development architecture work from product intent through design, implementation, testing, release, and operations. Use when the user asks for a complete development architecture, wants to know which Spellbook skills to combine, needs an execution path across…