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 override-upstreamgit 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/override-upstream)<a href="https://agentmods.dev/skills/apache/magpie/override-upstream"><img src="https://agentmods.dev/badge/skills/apache/magpie/override-upstream/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/override-upstream"><img src="https://agentmods.dev/badge/skills/apache/magpie/override-upstream.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.00049 | $0.04758 |
| Opus 5.5 | $0.00020 | $0.01903 |
| Sonnet 5.5 | $0.00010 | $0.00952 |
| Haiku 4.5 | $0.00005 | $0.00476 |
Grade A, and why
override-upstream 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 9d 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 — 342 lines — stays where its author put it; the contents beside it link to each section on GitHub.
setup-override-upstream
This skill turns a local override into a framework feature.
It takes one .apache-magpie-overrides/<skill>.md file in an adopter repo, helps the user decide whether the change is worth upstreaming, designs the framework-level abstraction, implements it in apache/magpie, and opens a PR.
Overrides (per docs/setup/agentic-overrides.md) are deliberately agentic and adopter-local: no schema, no anchors, no patch tool.
That makes them quick to write but hard to share, since every adopter who wants the same behaviour writes their own.
Upstreaming is the escape hatch: when an override starts looking like a missing feature, a PR bakes it into the framework default, and every adopter gets it on their next setup upgrade.
Adopter overrides
Before running its default behaviour, this skill consults
setup-override-upstream.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-override-upstream.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
1 file 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.
- 9d ago Changed · +1 lines b81de2c3e2ec
- 11d ago Changed · +6 lines cbfae57282e2
- 16d ago Changed 9d68f11e18e3
- 22d ago Changed · +8 lines 4fd7326775f5
- 28d ago Changed · -19 lines 78c43cbc5a8c
- 29d ago Changed · +1 lines 7c0f8a9b862f
- 1mo ago Changed · +1 lines e3ab8bcf1d9c
- 1mo ago Changed 500115be6524
- 1mo ago Changed · +72 lines d04f8253084c
- 1mo ago First seen · 272 lines · 49 tokens per session scan A 48dbbbf63329
override-upstream is a skill published in the GitHub repository apache/magpie (128 stars, last pushed yesterday), licensed Apache-2.0. It adds 49 tokens to every session and 4,758 once invoked, about $0.0002 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.
Other skills, from other repositories
bob-export
Create a Hacker Bob post-release improvement bundle for the currently installed Bob version.
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…
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…
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…
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
merge-pr
Merge a pull request with status checks, squash merge, and branch cleanup. Handles worktree contexts.