verify-release

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

A release-checking tool that waits for a published version to appear in the local plugin marketplace and then refreshes the installed-plugin registry. It can also run a dry check without changing anything.

In plain words
What is it for?
Use it after pushing a plugin release, when checking whether an installed plugin is outdated, or when diagnosing marketplace propagation with a timeout and polling interval.
Why use it?
It helps distinguish a failed release from a release that is still propagating. It also prevents the installed-version registry from being refreshed before the marketplace has caught up.

Skill for Claude CodeCodex

Part of the evo plugin — 26 skills, 27 commands, 107 agents, 3 hooks shipped together

Install

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.

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

Made for: Claude Code, Codex.

Or install evo, the plugin that ships this one along with the rest of its 26 skills, 27 commands, 107 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 verify-release

README.md
[![agentmods](https://agentmods.dev/badge/skills/mickeyyaya/evolve-loop/verify-release.svg)](https://agentmods.dev/skills/mickeyyaya/evolve-loop/verify-release)
Your own site
<a href="https://agentmods.dev/skills/mickeyyaya/evolve-loop/verify-release"><img src="https://agentmods.dev/badge/skills/mickeyyaya/evolve-loop/verify-release.svg" alt="Measured on agentmods" height="20"></a>
Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 730 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00060 $0.00730
Opus 5 $0.00030 $0.00365
Sonnet 5 $0.00012 $0.00146
Haiku 4.5 $0.00006 $0.00073

Measured 2d ago against content hash 27cfcdd1c98f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

verify-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 2d 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/verify-release/SKILL.md · 58 lines

How it starts

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

/evo:verify-release

Standalone post-publish propagation check. Polls the local marketplace checkout against an expected version, then refreshes installed_plugins.json registry. Use after a manual git push to confirm the new version actually landed, or when investigating "is my installed plugin out of date?"

What this skill does

Polls ~/.claude/plugins/marketplaces/evo/.claude-plugin/plugin.json against the target version. On match, runs legacy/scripts/utility/release.sh <target> to refresh the installed-plugins registry — closing the cache-refresh ordering bug structurally (release.sh only runs after convergence is confirmed).

The slash command translates to:

bash legacy/scripts/release/marketplace-poll.sh <args>

Invocation

/evo:verify-release 8.13.4                    # default: poll up to 5 min, 15s interval
/evo:verify-release 8.13.4 --max-wait-s 60    # shorter deadline (faster diagnostic)
/evo:verify-release 8.13.4 --poll-interval-s 5 # tighter loop, faster convergence detection
/evo:verify-release 8.13.4 --dry-run          # print poll params, don't pull or refresh

When to use this skill

  • After a manual ship that didn't go through /evo:publish (e.g., hot fix via bash legacy/scripts/lifecycle/ship.sh). The marketplace doesn't auto-pull; this verifies it caught up.
  • Diagnosing stale-plugin reports. If a user says "I'm running v8.13.2 but the marketplace shows v8.13.1," run /evo:verify-release 8.13.2 to force a marketplace pull and registry refresh.
  • After a git push origin main that used the explicit evolve guard ship --bypass emergency path.

When NOT to use this skill

  • During an in-flight /evo:publish run. The pipeline already polls internally. Running this concurrently could race against the pipeline's poll loop.
  • For non-evo marketplaces. This skill targets the evo marketplace specifically. Override the default path with --marketplace-dir <path> if you need to point elsewhere.

Read the full file on GitHub · 58 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. 2d ago First seen · 58 lines · 60 tokens per session scan A 27cfcdd1c98f

Subscribe to this mod's changes

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

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

ship

Pre-merge release pipeline: run tests, auto-scaled code review, version bump, changelog generation, git tag, push or PR. Auto-detects branch context (direct push on main, PR on feature branch). Scales review depth by diff size. Flags: --full, --no-bump, --no-tag, --dry-run, patch/minor/major.

greglas75/zuvo · 80 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