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.
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 apache/magpie --skill complete-upgradegit clone --depth 1 https://github.com/apache/magpieWrote 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/apache/magpie/complete-upgrade)<a href="https://agentmods.dev/skills/apache/magpie/complete-upgrade"><img src="https://agentmods.dev/badge/skills/apache/magpie/complete-upgrade/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/apache/magpie/complete-upgrade"><img src="https://agentmods.dev/badge/skills/apache/magpie/complete-upgrade.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.00062 | $0.06308 |
| Opus 5.5 | $0.00025 | $0.02523 |
| Sonnet 5.5 | $0.00012 | $0.01262 |
| Haiku 4.5 | $0.00006 | $0.00631 |
Grade B, and why
complete-upgrade scanned grade B with 1 finding 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 today.
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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Put a `[bypass]` *Check* item in the plan that reads `~/.claude/settings.json` and `~/.claude/settings.local.json` for `sandbox.enabled`, with the harness's own file-read tool (not Bash) or with the system `/usr/bin/jq` How it starts
The opening of the file, as written. The whole thing — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
setup-complete-upgrade
A new Magpie version arrives from outside any skill: a marketplace auto-update, /plugin update, a framework git pull, or setup upgrade on a pinned snapshot.
This skill brings the machine and the current project in line with it in one run.
It gathers what five existing skills check, shows one short plan, applies the approved items, re-checks, and ends with the exact commands for the rest.
It starts after the new version is installed.
It never updates plugins or the marketplace, never git pulls the framework, never bumps a snapshot, and never upgrades claude-code.
A pinned snapshot whose .apache-magpie.local.lock lags the committed .apache-magpie.lock is the one upgrade-shaped finding: it goes under Run these yourself as setup upgrade, never under Fix, and this run goes no further on it.
Invocation: /magpie-setup:complete-upgrade (marketplace), /magpie-setup-complete-upgrade (snapshot or self-adoption).
Adopter overrides
Before running its default behaviour, this skill consults
setup-complete-upgrade.md in the personal layer
(.apache-magpie-local/ when the project adopted Magpie, falling back to the main checkout's in a linked worktree,
or <git-common-dir>/apache-magpie/ when Magpie is only installed; applied first, wins on conflict) and
.apache-magpie-overrides/setup-complete-upgrade.md (committed, project-wide)
in the adopter repo, if present, and applies any agent-readable overrides it finds.
See docs/setup/agentic-overrides.md for the contract.
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.
- today Changed 294eb64bb778
- yesterday First seen · 276 lines · 62 tokens per session scan B 927508647843
complete-upgrade is a skill published in the GitHub repository apache/magpie (128 stars, last pushed yesterday), licensed Apache-2.0. It adds 62 tokens to every session and 6,308 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-26.
Other skills, from other repositories
aip-tracker
Track Airflow Improvement Proposal (AIP) implementation progress by comparing Confluence specs against codebase evidence. Use when asked to assess, report on, or compare AIP status.
bob-update
Check for Hacker Bob package updates and guide project-local update installation from Codex.
omv
Skill "omv" from bx33661/oh-my-vul, covering omv, commands, skills in this collection, registry and state directory.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
remove
Remove a deployed framework or addon from the current workspace.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…