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/kreek/consult/releasenpx skills add kreek/consult --skill releasegit clone --depth 1 https://github.com/kreek/consultWrote 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/kreek/consult/release)<a href="https://agentmods.dev/skills/kreek/consult/release"><img src="https://agentmods.dev/badge/skills/kreek/consult/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.00020 | $0.01725 |
| Opus 5 | $0.00010 | $0.00863 |
| Sonnet 5 | $0.00004 | $0.00345 |
| Haiku 4.5 | $0.00002 | $0.00172 |
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 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
Iron Law
BREAKING CHANGES BUMP MAJOR. AGENTS PREPARE RELEASES; HUMANS MUTATE SHARED ENVIRONMENTS.
When to Use
- The user explicitly asks for release prep, versioning, changelog work, release notes, tags, publish planning, rollout, rollback, deprecation, or migration notes.
- The user approves release prep after a concrete diff exposes release
artifacts or rollout obligations: manifests,
CHANGELOG.md, package locks, plugin/package metadata, CI/CD gates, feature flags, migrations, publish scripts, or rollout plans. - A repo validator requires release artifact sync for an already-approved change.
When NOT to Use
- Starting implementation because a change might later need versioning,
changelog, packaging, registry, rollout, or deployment work. Note release risk
in
workflowand ask only at the concrete release-prep decision point. - Triggering deploys, rollbacks, promotions, approvals, production config changes, feature-flag flips, DNS changes, infrastructure applies, or other shared-environment mutations. Prepare the command/checklist for a human.
- Internal refactors with no caller-visible impact; use
refactoring. - Local project bootstrap before release/deployment exists; use
scaffolding. - Database DDL/data safety itself; pair with
database. - Service monitoring and alert design; pair with
observability.
Core Ideas
- Release is a late gate. Implementation approval is not release approval. Load this skill only after user request, user approval, or a required validator sync.
- Release classification starts with the release unit and public surface. In monorepos, one library, CLI, plugin manifest, container, meta-package, or lockstep package set may each have different release streams.
- Compatibility uses the highest required bump for the release unit: breaking change is major, compatible addition is minor, fix/docs/internal is patch.
- Release artifacts must agree: manifest, committed lockfile, CHANGELOG header, tag plan, dependency ranges, package metadata, and publish order.
- Agents prepare release evidence, notes, checks, runbooks, and command plans. Humans mutate shared environments.
- Rollback must be faster than emergency fix-forward. Feature flags need owner, expiry, cleanup, safe default, and human-owned production change path.
What ships with it
2 files 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 First seen · 134 lines · 20 tokens per session scan A c1697832d004
release is a skill published in the GitHub repository kreek/consult (1 stars, last pushed 8d ago), licensed MIT. It adds 20 tokens to every session and 1,725 once invoked, about $0.0001 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-31.
Other skills, from other repositories
changelog-generation
Changelog generation skill for ZeroClaw releases. Use this skill when the user wants to generate a changelog, prepare release notes, or summarize what changed between versions. Trigger on: 'generate changelog', 'changelog for v0.7.x', 'prepare release notes', 'what changed since ', 'write the changelog'…
bump-version
Cut a new termio macOS release by tagging main with the next version. Invoke when the user says 'bump version', 'bump the version', 'cut a release', 'ship a new version', 'release', '发版', '发布新版本', or '出个新版本'.
generate-release-notes
Generate categorized release notes from any source (GitHub, Linear, Jira, or manual input) with optional publishing.
release
Cut a new gflow-cli release — bump version, update CHANGELOG, tag, push, and back-merge.
testflight-release
Ship a new TestFlight build of the iOS companion (TermioMobile) — resolve the next build number against App Store Connect, archive, sign, export, upload, write the What to Test notes, and distribute. Invoke when the user says 'ship a testflight build', 'update testflight', 'upload to testflight', 'new beta build'…
release
Project release helper for corezoid-ai-plugin. Prepares a new tagged release end-to-end. Use this skill whenever the user says "release", "релиз", "новый релиз", "сделай релиз", "выпусти версию", "bump version", "обновить версию", "tag a release", "/release", or anything that implies cutting a new version of this…