A read-only checklist for a staged release candidate. It checks signatures, checksums, licence and notice files, prohibited binary files, and links or references within the source tree.

Use it to verify release artefacts and source contents before approving a release candidate.

It helps catch integrity, licensing, packaging, and broken-reference problems before a release is published without changing the files.

verify-rc — Skill for Claude Code by apache/magpie

About the project

Apache Magpie is a framework of agent-assisted workflows for maintaining Apache software projects, including issue triage, pull-request review, contributor mentoring, and security-report handling. Apache maintainers and developers use it to delegate repetitive project work to coding agents while retaining human review. Its catalogue entries are the skills, instructions, plugin, and settings that implement these workflows.

apache/magpie · 120 stars · on GitHub · magpie.apache.org

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.

Any agent

npx skills add apache/magpie --skill verify-rc

Clone the repo

git clone --depth 1 https://github.com/apache/magpie

Made for: Claude Code.

Or install magpie-release-management, the plugin that ships this one along with the rest of its 10 skills.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/apache/magpie/verify-rc/github.svg)](https://agentmods.dev/skills/apache/magpie/verify-rc)

Your own site

<a href="https://agentmods.dev/skills/apache/magpie/verify-rc"><img src="https://agentmods.dev/badge/skills/apache/magpie/verify-rc/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/apache/magpie/verify-rc"><img src="https://agentmods.dev/badge/skills/apache/magpie/verify-rc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 99 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 6,364 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.

Model	Per session	Once invoked
Fable 5.1	$0.00099	$0.06364
Opus 5.5	$0.00040	$0.02546
Sonnet 5.5	$0.00020	$0.01273
Haiku 4.5	$0.00010	$0.00636

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

Security

Grade A, and why

verify-rc 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 4d 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.

plugins/magpie-release-management/skills/verify-rc/SKILL.md · 470 lines

How it starts

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

release-verify-rc

Pre-flight — is this project set up?

Do this first, before anything else in this skill, and do it silently. One command answers it and carries its own rules; there is nothing else to read.

Run the checker with this skill's own frontmatter name: and surface_hash:, and one --requires for each requires_config: entry:

PYTHONPATH=".apache-magpie-local:$(git rev-parse --git-common-dir)/../.apache-magpie-local:$(git rev-parse --git-common-dir)/apache-magpie" \
  python3 -m setup_preflight --skill <name> --hash <surface_hash> [--requires <file>]...

The path finds the checker /magpie-setup:setup config installed in the personal layer: this checkout's .apache-magpie-local/, the main checkout's when this is a linked worktree, or the git directory's apache-magpie/ when Magpie is only installed.

{"verdict": "ok"} → silent. Continue into the work the user asked for and say nothing about pre-flight. This is the ordinary answer.
{"verdict": "action", ...} → each finding names a section, and rules carries that section's text. Follow it. The facts are the inputs; what to propose, and what may not be done, are in the rules rather than here. Act on a finding only through its rules.
The command did not run at all — no such module, a non-zero exit, no python3 — → never read that as a pass, and do not re-derive the check by hand: it lives in code so that there is one version of it. If the project has no .apache-magpie.lock, .apache-magpie-overrides/, or personal layer (any of the three directories above), nothing has been set up here and there is nothing to reconcile — resolve this skill's requires_config: entries yourself (first match wins: .apache-magpie-local/<file>, the main checkout's .apache-magpie-local/<file>, <git-common-dir>/apache-magpie/<file>, then .apache-magpie-overrides/<file>), stay silent if they all resolve, and run /magpie-setup:setup config for this skill if any does not, which also installs the checker. Otherwise the project is set up and its checker is missing or stale: say so, propose /magpie-setup:setup config to install it or /magpie-setup:setup upgrade to refresh it, and carry on with the work.

Read the full file on GitHub · 470 lines

Files

What ships with it

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

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.

4d ago Changed · -217 lines 82240a9021ad
5d ago Changed · +2 lines 9f051487e2ab
7d ago Changed 7f41d14c1e0a
15d ago Changed · -63 lines · -152 tokens per session 91f7fc1ad519
16d ago Changed · -326 lines 2c2eb9e4d752
17d ago Changed · +116 lines · +44 tokens per session fa91cb5cda5e
21d ago Changed · -11 lines efae4da7af98
24d ago Changed · +1 lines 465255acc933
27d ago Changed · -4 tokens per session 9334e3c6165a
28d ago First seen · 968 lines · 211 tokens per session scan A 3dc36241d9ed

Subscribe to this mod's changes

verify-rc is a skill published in the GitHub repository apache/magpie (120 stars, last pushed today), licensed Apache-2.0. It adds 99 tokens to every session and 6,364 once invoked, about $0.0004 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-14.

CVE Claude Code Git and workflow Releases Security agent-skills apache automation

bob-export

Create a Hacker Bob post-release improvement bundle for the currently installed Bob version.

vmihalis/hacker-bob · 18 tokens

git-wrapup

Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…

cyanheads/nist-nvd-mcp-server · 120 tokens

release-and-publish

Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…

cyanheads/nist-nvd-mcp-server · 155 tokens

release-pr-review

Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…

cyanheads/nist-nvd-mcp-server · 136 tokens

release-announcement

Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.

paperclipai/paperclip · 42 tokens

release

Fully automate a release with version-bump and childhood.

thedotmack/claude-mem · 13 tokens