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-scanWrote 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-scan)<a href="https://agentmods.dev/skills/apache/magpie/security-issue-import-from-scan"><img src="https://agentmods.dev/badge/skills/apache/magpie/security-issue-import-from-scan.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.00098 | $0.03952 |
| Opus 5 | $0.00049 | $0.01976 |
| Sonnet 5 | $0.00020 | $0.00790 |
| Haiku 4.5 | $0.00010 | $0.00395 |
Grade A, and why
magpie-security-issue-import-from-scan 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
security-issue-import-from-scan
This skill is the scanner on-ramp of the security-issue handling process. It converts a security scanner's multi-finding output into security work — but, unlike the human-report on-ramps, it never defaults to import. A scan emits dozens of machine-generated findings, most of which are by-design, already-fixed, or below the CVE bar for the project's threat model. So the first-pass deliverable is a triage report; any tracker or PR is opt-in per the operator's reviewed decision.
It composes with:
security-issue-import— the Gmail on-ramp; this skill reuses its Step 2a fuzzy-dup search, its reject-pattern check, and its Step 7 tracker-creation path.security-issue-triage— whose Security-Model trust-boundary cheat-sheet and closed-invalid / positive-precedent searches do the actual classification.security-issue-fix— where a confirmed PR-worth finding becomes a public hardening PR.
The scan-format details (how to parse a given scanner's index +
evidence, the finding schema) live behind a pluggable adapter at
tools/scan-format/; ASVS is the
reference adapter. The project declares its scan sources and enabled
formats in <project-config>/project.md.
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 · 287 lines · 98 tokens per session scan A 7a738f566da0
magpie-security-issue-import-from-scan is a skill published in the GitHub repository apache/magpie (87 stars, last pushed 5d ago), licensed Apache-2.0. It adds 98 tokens to every session and 3,952 once invoked, about $0.0005 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
dast-nuclei
Fast, template-based vulnerability scanning using ProjectDiscovery's Nuclei with extensive community templates covering CVEs, OWASP Top 10, misconfigurations, and security issues across web applications, APIs, and infrastructure. Use when: (1) Performing rapid vulnerability scanning with automated CVE detection, (2)…
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
CSOC Operations & Playbook Automation
SOC alert triage, incident playbook automation, escalation workflows, shift reporting, and SOC KPI tracking.