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 issue-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/issue-triage)<a href="https://agentmods.dev/skills/apache/magpie/issue-triage"><img src="https://agentmods.dev/badge/skills/apache/magpie/issue-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/issue-triage"><img src="https://agentmods.dev/badge/skills/apache/magpie/issue-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00081 | $0.06389 |
| Opus 5.5 | $0.00032 | $0.02556 |
| Sonnet 5.5 | $0.00016 | $0.01278 |
| Haiku 4.5 | $0.00008 | $0.00639 |
Grade A, and why
issue-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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- triage — 88% identical, 524 lines differ
How it starts
The opening of the file, as written. The whole thing — 406 lines — stays where its author put it; the contents beside it link to each section on GitHub.
security-issue-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
6 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.
- 3d ago Changed · -138 lines 803da612db3a
- 5d ago Changed · +30 lines cf81ff61fda0
- 6d ago Changed · +2 lines fadb5c74f019
- 16d ago Changed · +7 lines f86ac5126a96
- 23d ago Changed · -113 lines · -49 tokens per session e54590bcad9f
- 24d ago Changed · -522 lines 7ca5a17ec961
- 25d ago Changed · +1 lines de00104b1a45
- 28d ago Changed · -4 tokens per session 0fbdaa18eba2
- 29d ago Changed · -94 lines e0053710e3b9
- 1mo ago First seen · 1,233 lines · 134 tokens per session scan A 7b12a44773cb
issue-triage is a skill published in the GitHub repository apache/magpie (121 stars, last pushed yesterday), licensed Apache-2.0. It adds 81 tokens to every session and 6,389 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
workflow-builder
Load before calling workflowbuilderbuildworkflow. Use for single-workflow work: new one-off workflows, existing-workflow edits, verification repairs, and workflow-local data tables. For any other new workflow, load intent-recognition first when it is listed. Write or edit a workspace source file, run workflow-sdk…
start-the-day
An on-demand personal daily briefing — weather, headlines, the shape of your day, and one thing worth your attention — in a sharp executive-assistant voice. The general-purpose morning brief; richer work or admin digests compose it as their general layer.
novu-design-workflow
Design notification workflows the Novu way — choose channels, set severity, decide when a workflow is critical, configure digests, and route based on subscriber state. Applies to BOTH dashboard-authored and code-first (@novu/framework) workflows. Use when planning a new workflow, deciding which channels to include…
naver-branding-post
A writing workflow for Naver blog posts about community planning, workshops, talks, and personal professional stories. It follows a defined visual style and shows the draft for approval before publication.
simplify
Improve existing work with focused simplification passes across code, writing, research, operations, or general tasks.
pulse-configure
Configure CocoPulse observation intervals and scopes.