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 pr-triagegit 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/pr-triage)<a href="https://agentmods.dev/skills/apache/magpie/pr-triage"><img src="https://agentmods.dev/badge/skills/apache/magpie/pr-triage/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/pr-triage"><img src="https://agentmods.dev/badge/skills/apache/magpie/pr-triage.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.00111 | $0.05010 |
| Opus 5.5 | $0.00044 | $0.02004 |
| Sonnet 5.5 | $0.00022 | $0.01002 |
| Haiku 4.5 | $0.00011 | $0.00501 |
Grade A, and why
pr-triage 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 — 389 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pr-management-triage
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
54 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.
- actions/approve-workflow.md 2.0 KB
- actions/close-stale.md 913 B
- actions/close.md 1.1 KB
- actions/comment.md 808 B
- actions/deliver-note.md 3.6 KB
- actions/draft.md 1.4 KB
- actions/mark-ready.md 1.7 KB
- actions/ping.md 797 B
- actions/promote-bot-draft.md 1.2 KB
- actions/rebase.md 978 B
- actions/request-author-confirmation.md 1.1 KB
- actions/rerun.md 1.0 KB
- actions/strip-ready-label.md 1.2 KB
- backport-check.md 3.9 KB
- classifications/already-triaged.md 2.1 KB
- classifications/author-confirmed-ready.md 1.4 KB
- classifications/awaiting-author-confirmation.md 774 B
- classifications/bot-draft.md 939 B
- classifications/first-time-stale-abandoned.md 1.2 KB
- classifications/flagged-author-close.md 1.3 KB
- classifications/flaky-ci-failure.md 791 B
- classifications/merge-conflict.md 1.1 KB
- classifications/no-real-ci.md 1000 B
- classifications/passing.md 1.2 KB
- classifications/pending-workflow-approval.md 1.6 KB
- classifications/quality-fallback.md 846 B
- classifications/security-language-signal.md 1.3 KB
- classifications/stale-copilot-review.md 2.0 KB
- classifications/stale-draft.md 616 B
- classifications/stale-review.md 930 B
- classifications/static-check-failure.md 1.1 KB
- classifications/sweep-1a-stale-triaged-draft.md 1.9 KB
- classifications/sweep-1b-stale-untriaged-draft.md 1.4 KB
- classifications/sweep-2-inactive-open.md 1.7 KB
- classifications/sweep-3-stale-workflow-approval.md 1.5 KB
- classifications/sweep-4-stale-ready-label.md 2.8 KB
- classifications/sweep-5-stale-confirmation-request.md 1.2 KB
- classifications/systemic-ci-failure.md 794 B
- classifications/threads-likely-addressed.md 2.1 KB
- classifications/unresolved-threads.md 1008 B
- classifications/unsettled-state.md 648 B
- contract-binding.md 1.8 KB
- design-notes.md 19 KB
- guards/mark_ready.py 2.9 KB runs code
- guards/mention.py 8.7 KB runs code
- interaction-loop.md 14 KB
- prerequisites.md 7.4 KB
- scripts/pr_link.py 4.5 KB runs code
- scripts/typed_decision_prefilter.py 29 KB runs code
- session-history.md 13 KB
- tests/test_pr_link.py 3.8 KB runs code
- tests/test_typed_decision_prefilter.py 24 KB runs code
- typed-decision-prefilter.md 2.7 KB
- workflow-approval.md 14 KB
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 1f806833dfd6
- 6d ago Changed · +3 lines 7a3feb6324b0
- 7d ago Changed f84ea27fc962
- 11d ago Changed · +9 lines 60944d716aa4
- 14d ago Changed 2785591ec5a3
- 17d ago Changed · -8 lines d88c7a5236f4
- 18d ago Changed · +2 lines 300897b49d5b
- 20d ago Changed · -588 lines · -13 tokens per session e8a51fb660bf
- 23d ago First seen · 969 lines · 124 tokens per session scan A 5c4829112ce7
pr-triage is a skill published in the GitHub repository apache/magpie (118 stars, last pushed today), licensed Apache-2.0. It adds 111 tokens to every session and 5,010 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-24.
Other skills, from other repositories
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…
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…