Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/acartine/foolery/ship-releasenpx skills add acartine/foolery --skill ship-releasegit clone --depth 1 https://github.com/acartine/fooleryWrote 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/acartine/foolery/ship-release)<a href="https://agentmods.dev/skills/acartine/foolery/ship-release"><img src="https://agentmods.dev/badge/skills/acartine/foolery/ship-release.svg" alt="Measured on agentmods" 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 | $0.00039 | $0.00563 |
| Opus 5 | $0.00019 | $0.00282 |
| Sonnet 5 | $0.00008 | $0.00113 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
ship-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 5d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ship-release
Cut a new release of foolery.
Principles
- Release from
main, not from a feature branch or implementation worktree. - Keep the worktree clean before starting.
- Sync
mainbefore previewing or running gates. - Do not use a PR workflow unless the user explicitly requests one.
- Do not manually recover by pushing ad hoc commits, tags, or GitHub releases. If the release path fails, fix the release script or the failing gate first.
Steps
-
Determine bump type — Ask whether this is a
patch,minor, ormajorrelease unless already specified, for example/ship-release patch. Show the current version and what each bump would produce. -
Preflight and sync — Confirm the repo is on
main, clean, and current:git status --short --branch git fetch origin main --tags git pull --ff-onlyIf
git pull --ff-onlychangesmain, continue from the updated commit. If it fails because the branch diverged or the worktree is dirty, stop and report the exact remediation. -
Preview changes — After syncing, run:
git log $(git describe --tags --abbrev=0)..HEAD --onelinePresent a brief summary so the user can confirm what is shipping.
-
Run quality gates — Execute in parallel:
bun run lint bunx tsc --noEmit bun run test bun run buildIf any gate fails, stop and report. Do not proceed with a broken release.
-
Cut the release — Run:
bun run release -- --<bump_type> --wait-for-artifactsThe release script performs its own final branch preflight, release quality gates, atomic branch/tag push, GitHub Release creation, artifact workflow wait, and asset verification. If
mainmoves during the final push, the script rebases the release commit onto the updated upstream, reruns the release quality gates, retags, and retries the atomic push. -
Report — Show the new version, link to the GitHub Release, and confirm the runtime tarballs and
.sha256files are available.
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.
- 5d ago First seen · 73 lines · 39 tokens per session scan A 48237d15e011
ship-release is a skill published in the GitHub repository acartine/foolery (54 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 563 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.
Other skills, from other repositories
versionup
Use when bumping the beads-starter on-demand plugin version by major, minor, or patch component and committing the result.
release
Author release notes, changelog, and signed release tag.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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.
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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.