Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jayvee/aigonnpx agentmods add skills/jayvee/aigon/releaseWrote 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/jayvee/aigon/release)<a href="https://agentmods.dev/skills/jayvee/aigon/release"><img src="https://agentmods.dev/badge/skills/jayvee/aigon/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.1 | $0.00079 | $0.01604 |
| Opus 5 | $0.00039 | $0.00802 |
| Sonnet 5 | $0.00016 | $0.00321 |
| Haiku 4.5 | $0.00008 | $0.00160 |
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 2d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
release
Three escalating actions, all wrapping scripts/ship.js. The mode is chosen by the user's intent — never escalate without asking.
git push share cut publish
│ │ │ │
no gate test:deploy + version+tag + npm publish
no tag + push branch + CHANGELOG (auto-routes
no version entry -beta→@next,
stable→@latest)
Step 0 — Ask mode first (MANDATORY, no exceptions)
Before doing anything else — even before running git commands — use AskUserQuestion to ask which mode they want. Do not infer from phrasing. Do not skip this step.
Question: "What kind of release do you want?"
Options:
- git push — push commits to origin, no tests, no version bump
- share — run test:deploy then push (no version tag)
- cut — version + tag + CHANGELOG entry (no npm publish)
- publish to npm — full release: tests + version + tag + npm publish
Only proceed to the steps below once the user has selected a mode.
share — npm run ship -- share
Runs test:deploy, pushes branch. No prompts beyond confirmation.
If the user just wants raw bytes off the laptop with no test gate (e.g. they committed scratch data), git push origin <branch> is correct — say so and run it. Don't escalate to share reflexively.
cut and publish — same flow, different final command
1. Pre-flight checks
Run in parallel:
git status --short— must be empty. If not, list files and stop.git rev-list origin/main..HEAD --count— must be > 0. Else "nothing to ship".git rev-parse --abbrev-ref HEAD— should bemain. Else warn + confirm.
2. Choose version
Read current state:
- Current version:
node -p "require('./package.json').version" - Latest tag:
git describe --tags --abbrev=0
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.
- 2d ago First seen · 128 lines · 79 tokens per session scan A 5d900e577048
release is a skill published in the GitHub repository jayvee/aigon (25 stars, last pushed 5d ago), licensed Apache-2.0. It adds 79 tokens to every session and 1,604 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-credit-harvest
Harvest one community PR into a release branch with authorship and credit preserved, verified green, and a warm thank-you.
release
Prepare a named version: preflight, version consistency, build/package, smoke test, checksums/notes, and release readiness. Publishing/tagging/deploy need separate authorization. Explicit-only.
release
Cut and publish a full stable NAC release after main, release-PR, and publication CI pass. Use when a maintainer asks for a stable version bump, tag, or GitHub Release. Never use for release candidates; NAC RC releases are automated.
release-expert
Multi-repo release coordination: version alignment, RC lifecycle, release waves, rollback planning. Use when saying "release", "version alignment", or "cut an RC".
agentplane-release-and-packaging-operator
Use when preparing, validating, publishing, auditing, or recovering an Agentplane release, especially package build ordering, version parity, npm/GitHub/GHCR/external distribution publication, public install smoke tests, hosted publish evidence, or release CI failures.