Borrowing it
Nothing to install: this file belongs to onevcat/argue. 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/onevcat/argue/master/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/onevcat/argueWrote 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/onevcat/argue/release)<a href="https://agentmods.dev/skills/onevcat/argue/release"><img src="https://agentmods.dev/badge/skills/onevcat/argue/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/onevcat/argue/release"><img src="https://agentmods.dev/badge/skills/onevcat/argue/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00027 | $0.01228 |
| Opus 5.5 | $0.00011 | $0.00491 |
| Sonnet 5.5 | $0.00005 | $0.00246 |
| Haiku 4.5 | $0.00003 | $0.00123 |
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 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.
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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
Prepare and ship a new version of argue packages.
Pre-conditions
- Working tree is clean (
git statusshows no uncommitted changes) - You are on the
masterbranch - All CI checks pass locally (
npm run ci && npm run format:check)
If any pre-condition fails, fix it before proceeding. Do NOT skip checks.
Step 1 — Gather Context
Run these commands and record the output:
# Current unified version (root is the source of truth)
node -e "import('./package.json',{with:{type:'json'}}).then(m=>console.log('workspace:',m.default.version))"
# Last release tag
git tag -l 'v*' --sort=-v:refname | head -1
# Commits since last tag (or all if no tag)
LAST_TAG=$(git tag -l 'v*' --sort=-v:refname | head -1)
if [ -n "$LAST_TAG" ]; then
git log "$LAST_TAG"..HEAD --oneline
else
git log --oneline
fi
Step 2 — Decide Version Bump
Based on the commits gathered above, determine the semver bump:
| Commit pattern | Bump |
|---|---|
fix: / perf: / refactor: only |
patch |
Any feat: |
minor |
BREAKING CHANGE in body or !: in type |
major |
All workspace packages share one version number. Pick the highest bump level across all commits.
Present the decision to the user:
Current version: X.Y.Z Commits since last release: (count) Suggested bump: patch/minor/major -> X.Y.Z
Proceed?
Wait for confirmation. The user may override the version.
Step 3 — Update Versions
node scripts/bump-version.mjs X.Y.Z
npm install
This updates version in the root package.json and every packages/*/package.json, and rewrites @onevcat/argue-cli and @onevcat/argue-viewer's internal dependency on @onevcat/argue to ^X.Y.Z.
Step 4 — Generate Changelog
Read the current CHANGELOG.md (create if it doesn't exist). Prepend a new section at the top (after the # Changelog heading).
Format:
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 First seen · 137 lines · 27 tokens per session scan A a21be5817214
release is a skill published in the GitHub repository onevcat/argue (282 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 1,228 once invoked, about $0.0001 per session on Opus 5.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
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
Fully automate a release with version-bump and childhood.
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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
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.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.