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
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/apache/magpienpx agentmods add skills/apache/magpie/security-issue-import-from-mdWrote 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-import-from-md)<a href="https://agentmods.dev/skills/apache/magpie/security-issue-import-from-md"><img src="https://agentmods.dev/badge/skills/apache/magpie/security-issue-import-from-md.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.00073 | $0.08599 |
| Opus 5 | $0.00036 | $0.04300 |
| Sonnet 5 | $0.00015 | $0.01720 |
| Haiku 4.5 | $0.00007 | $0.00860 |
Grade A, and why
magpie-security-issue-import-from-md 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 — 815 lines — stays where its author put it; the contents beside it link to each section on GitHub.
security-issue-import-from-md
This skill is the batch on-ramp of the security-issue handling
process for the case where the security team has a markdown file
containing one or more pre-formatted security findings — typically
the output of an AI security review run against an <upstream>
branch, or a third-party scanner exporting in a similar shape. It
parses each finding in the file and creates one <tracker> tracking
issue per finding, landing them in Needs triage so the standard
validity discussion (Step 3 of README.md)
can run.
It is the third on-ramp variant alongside the two existing import skills:
security-issue-import |
security-issue-import-from-pr |
security-issue-import-from-md |
|
|---|---|---|---|
| Source | <security-list> Gmail / PonyMail thread |
<upstream> PR URL or number |
Markdown file with one or more findings |
| Reporter | External researcher | None (PR author = remediation developer) | None (the file is the report; usually AI- or scanner-generated) |
| Receipt-of-confirmation reply | Drafted on the inbound thread | Skipped — no reporter to reply to | Skipped — no reporter to reply to |
| Validity assessment | Hosted on the tracker after import | Already done informally before invocation | Hosted on the tracker after import |
| Initial board column | Needs triage |
Assessed |
Needs triage |
| Cardinality | One thread → one tracker | One PR → one tracker | One file → N trackers |
Golden rule — every finding lands as Needs triage. A
markdown file (especially an AI-generated one) is a proposal of
findings, not an assessment. Each tracker created by this skill
must go through the same Step 3 validity discussion as a Gmail-
imported tracker. The skill must not pre-assess findings based on
their **Severity:** tag, must not skip the validity step for
findings tagged HIGH, and must not auto-allocate CVEs.
Golden rule — confidentiality. The input markdown file is
private security-team material. Treat it the same as
<security-list> content per the
Confidentiality of <tracker>
rule: paste verbatim into the (private) tracker is fine; never
paste into a public surface — not into <upstream>, not into a
public GHSA, not into any comment on a public repo. The ## Location
URL fields commonly point at public branches / files; that is fine
to render as-is in the tracker (the URL is already public), but do
not propagate the surrounding security framing to the public
surface the URL points at.
Golden rule — propose every finding individually before applying.
Even when the input is a 50-finding file, the skill surfaces a
proposal table listing every finding and waits for explicit
confirmation. The default disposition mirrors security-issue-import:
import all unless rejected upfront (skip N to drop a specific
candidate). A bare go / proceed / yes, all imports every
non-rejected candidate. The skill must still render each candidate
in the proposal so the user can scan and override.
Golden rule — every <tracker> / <upstream> reference is
clickable in the surface it lands on. Whenever this skill emits
a reference to a tracker issue, PR, or comment — the proposal
table shown before import, the created tracker issue bodies, the
duplicate-tracker guard cross-links, the recap output listing what
was created — the reference must be one click away in whatever
surface it lands on:
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 · 815 lines · 73 tokens per session scan A d8d7524997d9
magpie-security-issue-import-from-md is a skill published in the GitHub repository apache/magpie (87 stars, last pushed 5d ago), licensed Apache-2.0. It adds 73 tokens to every session and 8,599 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-09-03.
Other skills, from other repositories
persona-project-manager
Coordinate projects — track tasks, schedule meetings, and share docs.
persona-event-coordinator
Plan and manage events — scheduling, invitations, and logistics.
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.