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 code-reviewgit 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/code-review)<a href="https://agentmods.dev/skills/apache/magpie/code-review"><img src="https://agentmods.dev/badge/skills/apache/magpie/code-review/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/code-review"><img src="https://agentmods.dev/badge/skills/apache/magpie/code-review.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.00089 | $0.03790 |
| Opus 5.5 | $0.00036 | $0.01516 |
| Sonnet 5.5 | $0.00018 | $0.00758 |
| Haiku 4.5 | $0.00009 | $0.00379 |
Grade A, and why
code-review 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 yesterday.
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 — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pr-management-code-review
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, andrulescarries that section's text. Follow it. Thefactsare 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'srequires_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 configfor 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 configto install it or/magpie-setup:setup upgradeto refresh it, and carry on with the work.
What ships with it
48 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.
- adopter-config.md 1.6 KB
- adversarial.md 12 KB
- background-subagents.md 6.6 KB
- budget-discipline.md 637 B
- classifications/backport.md 1.3 KB
- classifications/disposition-approve.md 707 B
- classifications/disposition-comment.md 591 B
- classifications/disposition-request-changes.md 701 B
- classifications/footer-approve.md 688 B
- classifications/footer-comment-maintainer.md 776 B
- classifications/footer-comment-role-neutral.md 773 B
- classifications/footer-request-changes.md 704 B
- classifications/security-disclosure.md 1.7 KB
- classifications/selector-area.md 801 B
- classifications/selector-ready.md 491 B
- classifications/selector-single-pr.md 595 B
- classifications/selector-team.md 554 B
- classifications/skip-draft.md 315 B
- classifications/skip-prior-approval-current-sha.md 611 B
- classifications/skip-prior-approval-stale-sha.md 507 B
- classifications/skip-self-authored.md 440 B
- classifications/skip-wip-title.md 273 B
- classifications/skip-zero-diff.md 261 B
- classifications/slop-early-exit.md 4.8 KB
- classifications/slop-note-only.md 1.1 KB
- classifications/stacked-layer.md 629 B
- criteria.md 5.9 KB
- criteria/ai-generated-code-signals.md 3.7 KB
- criteria/api-correctness.md 535 B
- criteria/architecture-boundaries.md 543 B
- criteria/code-quality.md 532 B
- criteria/commits-and-prs.md 585 B
- criteria/database-query-correctness.md 548 B
- criteria/generated-files.md 535 B
- criteria/image-ip.md 1.2 KB
- criteria/license-headers.md 6.5 KB
- criteria/quality-signals-to-check.md 1.4 KB
- criteria/security-model.md 1.6 KB
- criteria/testing.md 527 B
- criteria/third-party-license-compliance.md 2.9 KB
- criteria/ui.md 541 B
- invocation.md 3.8 KB
- posting.md 11 KB
- prerequisites.md 7.9 KB
- review-flow.md 20 KB
- review-loop.md 448 B
- scope.md 2.7 KB
- session-summary.md 771 B
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.
- yesterday Changed · +2 lines 406cc058ea89
- 6d ago Changed · -102 lines 2ebf8a41c7bf
- 10d ago Changed 84753f625698
- 11d ago Changed · +7 lines 531b78c311b8
- 17d ago Changed f68de0038feb
- 18d ago Changed fac139d15bdb
- 20d ago Changed · -326 lines · -8 tokens per session d70e29fcecee
- 22d ago Changed · +4 lines 0d1a0aa49ff8
- 23d ago Changed · -4 tokens per session 89bd1cc90174
- 24d ago First seen · 715 lines · 101 tokens per session scan A 7ffe3135ee18
code-review is a skill published in the GitHub repository apache/magpie (118 stars, last pushed today), licensed Apache-2.0. It adds 89 tokens to every session and 3,790 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.
Other skills, from other repositories
tech-debt
Track, categorize and prioritize technical debt across the codebase — scans for debt indicators, maintains a register.
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
maintain
Triage and work through Ouroboros GitHub issues and pull requests as a maintainer. Use for ooo maintain, backlog cleanup, review, merge readiness, duplicate PRs, and issue disposition.
spec-kitty-runtime-review
Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…
ring:planning-large-features
Planning the 8-gate Large Track pre-dev workflow (research, PRD, feature map, TRD, API contract, data model, dependency map, plan) with per-gate human approval. Use for features 2+ days that add dependencies, data models, multi-service integration, or new architecture. Skip for small features (use…