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 agentmods add skills/apache/magpie/issue-reassess-statsnpx skills add apache/magpie --skill issue-reassess-statsgit 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/issue-reassess-stats)<a href="https://agentmods.dev/skills/apache/magpie/issue-reassess-stats"><img src="https://agentmods.dev/badge/skills/apache/magpie/issue-reassess-stats.svg" alt="Measured on agentmods" 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 | $0.00083 | $0.02393 |
| Opus 5 | $0.00042 | $0.01196 |
| Sonnet 5 | $0.00017 | $0.00479 |
| Haiku 4.5 | $0.00008 | $0.00239 |
Grade A, and why
magpie-issue-reassess-stats 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.
How it starts
The opening of the file, as written. The whole thing — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
issue-reassess-stats
Read-only dashboard skill over the verdict.json artefacts
produced by issue-reassess
campaigns. Surfaces a health rating, classification distribution,
the still-fails-* action tail, partial-fix surfaces, new-issue
candidates from cross-family probes, and per-component breakdowns.
The skill is the read-only counterpart to
issue-reassess — both consume the
same on-disk artefacts. Where reassess writes verdicts (one
per candidate) and a report.md, this skill renders an at-a-
glance dashboard for the maintainer to scan.
Modelled on pr-management-stats.
Golden rules
Golden rule 1 — read-only on tracker AND on campaign
artefacts. This skill reads verdict.json files and emits HTML.
It does not modify any campaign artefact, does not post to
<issue-tracker>, does not re-invoke issue-reproducer.
Golden rule 2 — HTML by default. The dashboard is designed for
the "what should I do today" glance. Markdown and tables-only
fallbacks are available for terminal pipelines (--markdown,
--tables-only).
Golden rule 3 — surface action candidates first. The dashboard opens with the still-failing-bug count and the new-issue candidates from probes — these are where work happens. The bulk fixed-on-master / cannot-run-* counts come second.
What ships with it
4 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.
- 4d ago First seen · 272 lines · 83 tokens per session scan A b8b71b518074
magpie-issue-reassess-stats is a skill published in the GitHub repository apache/magpie (87 stars, last pushed 3d ago), licensed Apache-2.0. It adds 83 tokens to every session and 2,393 once invoked, about $0.0004 per session on Opus 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-08-30.
Other skills, from other repositories
magpie-setup
Adopt and maintain the apache-magpie framework in a project repo via the snapshot-based adoption mechanism. The only framework skill committed in an adopter's repo; every other skill is a symlink the adopt sub-action wires up. Sub-actions: /magpie-setup - first-time adoption (default; main-checkout only) /magpie-setup…
upgrade-fab-provider
Upgrade the pinned Flask-AppBuilder (FAB) dependency in the Apache Airflow FAB provider (providers/fab/). Bumps the exact flask-appbuilder== pin and its mirror constant, regenerates uv.lock, drives the testfabalignment.py drift tripwire, reviews the vendored security-manager override.py against the new upstream FAB…
aip-user-stories
Generate verified recipe playbooks from AIPs with PR implementations (post mode), or speculative user stories from AIPs without implementations (pre mode). Use when the user provides an AIP URL or AIP content, optionally with PR URLs and file paths.
airflow-new-sdk
Guide for implementing a brand-new language SDK for Airflow (AIP-108). Use this skill when a contributor wants to add support for a new programming language — designing the Python coordinator, implementing the wire protocol in the target language, writing the bundle format, and structuring the PR. Trigger on phrases…
airflow-java-sdk
Guide for contributing to the Airflow Java SDK (AIP-108). Use this skill whenever a contributor is working in the java-sdk/ directory or on the Java coordinator in task-sdk/src/airflow/sdk/coordinators/java/ — whether they want to add a feature, write tests, fix a bug, understand the architecture, or prepare a PR.…
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.