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 security-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/security-issue-triage)<a href="https://agentmods.dev/skills/apache/magpie/security-issue-triage"><img src="https://agentmods.dev/badge/skills/apache/magpie/security-issue-triage.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.1 | $0.00134 | $0.12660 |
| Opus 5 | $0.00067 | $0.06330 |
| Sonnet 5 | $0.00027 | $0.02532 |
| Haiku 4.5 | $0.00013 | $0.01266 |
Grade A, and why
magpie-security-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.
How it starts
The opening of the file, as written. The whole thing — 1,087 lines — stays where its author put it; the contents beside it link to each section on GitHub.
security-issue-triage
This skill is the initial-triage discussion-starter for security
tracker issues. For each <tracker>
issue carrying the needs triage label, it reads the body + comments,
applies the project's Security Model framing, classifies the candidate
disposition, and — on the user's explicit confirmation — posts a
triage-proposal comment that invites the security team to react.
The skill never flips needs triage to a scope label, never
closes, never allocates a CVE, never edits the body. The
valid / invalid decision belongs to team consensus; this skill opens
the discussion that produces it, and the sibling skills below apply
the state change once consensus lands.
It composes with:
security-issue-import— the on-ramp that createsNeeds triagetrackers; triage is the natural next step after a batch lands.security-cve-allocate— invoked by hand after the team agrees a tracker is VALID.security-issue-invalidate— invoked by hand after the team agrees a tracker is INVALID or INFO-ONLY.security-issue-deduplicate— invoked by hand after the team agrees a tracker is a PROBABLE-DUP.security-issue-sync— picks up after the team's decision lands; flipsneeds triage→ scope label, records the disposition in the rollup, and propagates to the project board.
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 First seen · 1,087 lines · 134 tokens per session scan A aa73afe896c5
magpie-security-issue-triage is a skill published in the GitHub repository apache/magpie (87 stars, last pushed 5d ago), licensed Apache-2.0. It adds 134 tokens to every session and 12,660 once invoked, about $0.0007 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-09-03.
Other skills, from other repositories
persona-event-coordinator
Plan and manage events — scheduling, invitations, and logistics.
persona-project-manager
Coordinate projects — track tasks, schedule meetings, and share docs.
persona-team-lead
Lead a team — run standups, coordinate tasks, and communicate.
recipe-plan-weekly-schedule
Review your Google Calendar week, identify gaps, and add events to fill them.
atmos-migration
This skill helps you migrate a repository to Atmos. It covers native Terraform, Terraform Workspaces, Terramate, Terragrunt, Makefiles, Justfiles, and Taskfiles. It gives minimum-disruption paths, file-layout options, workspace mapping, task-to-command mapping, generatehcl/script decomposition, and the remote-state…
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.