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 skills add Chemaclass/agnostic-ai --skill cut-releasegit clone --depth 1 https://github.com/Chemaclass/agnostic-aiWrote 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/chemaclass/agnostic-ai/cut-release)<a href="https://agentmods.dev/skills/chemaclass/agnostic-ai/cut-release"><img src="https://agentmods.dev/badge/skills/chemaclass/agnostic-ai/cut-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/chemaclass/agnostic-ai/cut-release"><img src="https://agentmods.dev/badge/skills/chemaclass/agnostic-ai/cut-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.00031 | $0.01860 |
| Opus 5.5 | $0.00012 | $0.00744 |
| Sonnet 5.5 | $0.00006 | $0.00372 |
| Haiku 4.5 | $0.00003 | $0.00186 |
Grade A, and why
cut-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 3d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cut-release
Cuts a new release of agnostic-ai. The release commit carries the version,
exact changelog, and one public release briefing. GoReleaser publishes
artifacts and the GitHub Release once the tag is pushed. Pages publishes the
briefing from the same commit on main.
Scope
Use this workflow when the user asks to publish a new version. A request to prepare release material stops before pushing or tagging; preserve any narrower scope from the user. On later release authorization, inspect the prepared version, changelog, briefing, and working changes, then resume at the first incomplete step. Preserve recognized release edits; do not repeat the changelog rollover. Reuse checks only while their inputs remain unchanged.
Steps
-
Confirm
mainand a clean working tree for a new release, thengit pull --ff-only. For resumed preparation with uncommitted release edits, fetch and inspect remote changes without discarding that work; reconcile an advanced base before validation. -
Use the requested version, or select the next version from the changes since the last tag (
git log --oneline <last-tag>..HEAD). Check diffs and migration notices as well as commit types; the changelog groups by scope, not kind:- patch: bug fixes only
- minor: additive features
- major: breaking changes after v1.0; while on 0.x, use a minor release
with explicit breaking notes, as required by
spec-migration
-
Update
CHANGELOG.md: drop empty###and####headings from## [Unreleased], then move the remaining lines into a new dated## vX.Y.Z - YYYY-MM-DDsection (no brackets). The released section must never carry a heading with no entries. Reset## [Unreleased]to empty.Curate the section first with the layout, entry rules, and length check in
.agnostic-ai/agents/changelog-curator.md. Condensing keeps every#NNN. A path, flag, or case it drops must already be on the docs page or in the PR; if it is not, add it to the docs, not back to the bullet.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago Changed · +18 lines 22540a50a0e1
- 16d ago Changed · +2 lines d55722c75f11
- 18d ago Changed 3a97660c7102
- 20d ago Changed · +7 lines 84479f209e4d
- 25d ago Changed · +5 lines 10914d33af2d
- 27d ago Changed · +6 lines a6bbf78e0c07
- 29d ago Changed 7eb7c043a7b1
- 1mo ago Changed · -7 lines 6d3d95a9147d
- 1mo ago Changed · +2 lines 63ba5637a20d
- 1mo ago First seen · 85 lines · 31 tokens per session scan A 522387442139
cut-release is a skill published in the GitHub repository Chemaclass/agnostic-ai (25 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 1,860 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
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
release
Use this skill for EVERY ClawRouter release. Enforces the full checklist — version sync, CHANGELOG, build, tests, npm publish, git tag, GitHub release. No step can be skipped.