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.00408 |
| Opus 5 | $0.00015 | $0.00204 |
| Sonnet 5 | $0.00006 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
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 10d 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.
What it actually says
cut-release
Cuts a new release of agnostic-ai. GoReleaser publishes artifacts and the GitHub Release once the tag is pushed.
When to run
The user asks to release, tag, ship, or cut a new version.
Steps
- Confirm working tree clean and on
main.git pull --ff-only. make preflight(fmt-check + vet + lint + test). Refuse to proceed on any failure.- Decide next version per semver:
- patch: bug fixes only
- minor: additive features
- major: breaking changes
- Update
CHANGELOG.md: drop empty###subsections 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. - Bump
versionincmd/agnostic-ai/main.go. - Commit:
chore(release): vX.Y.Z. GPG-signed. - Tag:
git tag -s vX.Y.Z -m "vX.Y.Z". - Push branch and tag:
git push && git push origin vX.Y.Z. - Watch the GoReleaser workflow. If it fails, fix root cause. Do not delete and retag without clear reason.
Conventions
- Release notes pipeline reads the latest dated section from
CHANGELOG.md. Never skip step 4. - Tag format
vX.Y.Z(lowercasev). GoReleaser matches this prefix. - Commit message follows Conventional Commits. Never mention AI in the message.
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.
- 10d ago First seen · 34 lines · 31 tokens per session scan A e6cc97897bd1
cut-release is a skill published in the GitHub repository Chemaclass/agnostic-ai (12 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 408 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
ship-pr
Ship one pull request, monitor hosted CI and review feedback, follow PR policy, and request authorization before merging and cleaning up.
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.
changelog-scan
Scan merged PRs and commits since a given reference, extract titles, labels, types, and signals. Produces structured input for release notes drafting.
draft-release-notes
Turn changelog-scan output into polished, categorized release notes draft. Propose only.
release-notes
Create release notes for a new version tag. Gathers all commits, PRs, issues fixed, and breaking changes since a previous release. Creates the release notes markdown file, tags the repo, and pushes. Asks the user to confirm the base version to diff against.