agentmods.dev

release

release is a skill for Claude Code from mickeyyaya/evolve-loop. It costs 69 tokens per session (777 once invoked), scanned A, original, Apache-2.0.

A read-only release readiness check that verifies whether a project meets its publishing criteria before the actual release process runs.

In plain words
What is it for?
Use it to confirm that CI is green, release checks pass, version markers agree, and the branch is ready for the publishing workflow.
Why use it?
It finds issues such as failing checks, an unclean working tree, missing version consistency, or unfinished commits before publishing.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is Release **readiness-gate**, not a release executor. It composes the checks that already exist (`evolve release-preflight`, `evolve release-consistency`), then h.

Part of the evo plugin — 33 skills, 34 commands, 99 agents, 3 hooks shipped together

not rated 6repo changed 6d ago A scan 69 tokens original Apache-2.0

Good fit Use it to confirm that CI is green, release checks pass, version markers agree, and the branch is ready for the publishing workflow.

Compare 6 skills from other repositories ↓
View source ↗ mickeyyaya/evolve-loop mickeyyaya.github.io
Install

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.

Clone the repo
git clone --depth 1 https://github.com/mickeyyaya/evolve-loop
agentmods
npx agentmods add skills/mickeyyaya/evolve-loop/release

Made for: Claude Code.

Or install evo, the plugin that ships this one along with the rest of its 33 skills, 34 commands, 99 agents, 3 hooks.

Wrote 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.

agentmods badge for release

README.md
[![agentmods](https://agentmods.dev/badge/skills/mickeyyaya/evolve-loop/release/github.svg)](https://agentmods.dev/skills/mickeyyaya/evolve-loop/release)
Your own site
<a href="https://agentmods.dev/skills/mickeyyaya/evolve-loop/release"><img src="https://agentmods.dev/badge/skills/mickeyyaya/evolve-loop/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.

agentmods 80×15 button for release

Your own site · 80×15
<a href="https://agentmods.dev/skills/mickeyyaya/evolve-loop/release"><img src="https://agentmods.dev/badge/skills/mickeyyaya/evolve-loop/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 777 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00069 $0.00777
Opus 5.5 $0.00028 $0.00311
Sonnet 5.5 $0.00014 $0.00155
Haiku 4.5 $0.00007 $0.00078

Measured 6d ago against content hash ec30774e95c6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 6d 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.

skills/release/SKILL.md · 50 lines

How it starts

The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/evo:release

Release readiness-gate, not a release executor. It composes the checks that already exist (evolve release-preflight, evolve release-consistency), then hands a green report to /evo:publish, which owns the actual bump → changelog → ship → propagate lifecycle.

Why this exists

evolve release-preflight gates: clean tree, attached branch, semver bump, recent audit PASS and gate-test suites. It also refuses WIP commits since the last tag and a red required.yml CI verdict of HEAD. With --require-ci, an unavailable CI verdict (no run visible, or no gh) also fails. evolve release-consistency verifies the 6 version markers (plugin.json, marketplace.json, README, CHANGELOG, SKILL headings). This skill runs both and reports one verdict — nothing more.

Defense-in-depth: /evo:publish now performs the same pre-release CI-green check itself (so a direct /evo:publish call is still gated) and adds a post-release watch of the released commit's required CI and release workflows. Running /evo:release first stays the recommended path; evolve release (the raw binary) is gh-free and only prints a "CI not verified" advisory.

Procedure

Run in order. Any FAIL → print the reason and stop (do not delegate to /evo:publish).

  1. Preflight — read-only. Do not pass --dry-run: a dry run skips the WIP and CI gates. 
    $CLAUDE_PROJECT_DIR/go/bin/evolve release-preflight <target> --require-ci
    Non-zero exit → stop. The output names the failing check. A WIP failure lists each subject that matches ^(WIP|fixup!|squash!|amend!). A CI failure gives the run URL.
  2. Consistency (version markers): 
    $CLAUDE_PROJECT_DIR/go/bin/evolve release-consistency <target>
    Non-zero exit → stop.
  3. Main is current — confirm git rev-parse HEAD equals git rev-parse origin/main, because the preflight checks the CI run of HEAD. A mismatch → stop.
  4. All green → delegate: invoke /evo:publish <target> (pass --dry-run through if the user gave it). Report the readiness summary first so the user sees what passed.

Read the full file on GitHub · 50 lines

Changes

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.

  1. 6d ago Changed · -10 lines · -14 tokens per session ec30774e95c6
  2. 24d ago Changed 5fe7cc4dae66
  3. 1mo ago First seen · 60 lines · 83 tokens per session scan A 8d97904d305e

Subscribe to this mod's changes

release is a skill published in the GitHub repository mickeyyaya/evolve-loop (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 69 tokens to every session and 777 once invoked, about $0.0003 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-09-03.

Claude CodeGit and workflowReleasesai-agentsai-pipelineautonomous-codingclaude-code-plugincode-quality
Related

Other skills, from other repositories

release

Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…

hyhmrright/brooks-lint · 135 tokens

bump-version

Bump the Logic-Lens version across all six metadata locations at once (package.json, the four plugin manifests, and the README badge), then validate. Use when cutting a release or when npm run validate reports a version mismatch.

hyhmrright/logic-lens · 52 tokens

release-docs

Diff-driven documentation sync after a release. Determines what source files changed, delegates changelog to zuvo:docs, updates only docs whose source changed. Flags: --dry-run, explicit range argument.

greglas75/zuvo · 44 tokens

changelog

Add CHANGELOG.md entries, derive them from commits, or cut a Keep a Changelog and SemVer release.

reidemeister94/development-skills · 26 tokens

sw-ship

Ships the current work unit. Verifies all gates passed, creates a PR with evidence-mapped body, updates workflow state to shipped.

Obsidian-Owl/specwright · 31 tokens

push-ci

Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).

sd0xdev/sd0x-harness · 82 tokens