magpie-security

magpie-security is a plugin for Claude Code from apache/magpie. Its manifest loads nothing; the 15 skills it bundles cost 1,036 tokens per session together, scanned A, original, Apache-2.0.

A maintainer-only toolkit for handling software security issues, from initial import through triage, duplicate checking, invalidation, and CVE publication. A CVE is a public identifier for a known security vulnerability.

In plain words
What is it for?
Importing, triaging, synchronising, deduplicating, invalidating, and publishing CVE-related security issues.
Why use it?
It organises the security-issue lifecycle so reports and public vulnerability records can be handled consistently.

Plugin for Claude Code ✓ vendor

Written for Claude Code: a Claude Code plugin manifest.

Good fit Importing, triaging, synchronising, deduplicating, invalidating, and publishing CVE-related security issues.

Compare 6 plugins from other repositories ↓
Install in Claude Code
/plugin marketplace add apache/magpie
/plugin install magpie-security
About the project

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.

apache/magpie · 120 stars · on GitHub · magpie.apache.org

Install

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.

Clone the repo
git clone --depth 1 https://github.com/apache/magpie

Made for: Claude Code.

Wrote 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.

agentmods badge for magpie-security

README.md
[![agentmods](https://agentmods.dev/badge/plugins/apache/magpie/magpie-security/github.svg)](https://agentmods.dev/plugins/apache/magpie/magpie-security)
Your own site
<a href="https://agentmods.dev/plugins/apache/magpie/magpie-security"><img src="https://agentmods.dev/badge/plugins/apache/magpie/magpie-security/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.

agentmods 80×15 button for magpie-security

Your own site · 80×15
<a href="https://agentmods.dev/plugins/apache/magpie/magpie-security"><img src="https://agentmods.dev/badge/plugins/apache/magpie/magpie-security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured The manifest loads nothing itself; its 15 skills cost 1,036 tokens a session between them.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

magpie-security 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 yesterday.

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.

plugins/magpie-security/.claude-plugin/plugin.json · 14 lines

What it actually says

{
  "name": "magpie-security",
  "description": "Apache Magpie \u2014 security-issue handling lifecycle \u2014 import through CVE publication, triage, sync, dedup, invalidate. Maintainer-only.",
  "version": "0.9.0.dev202610192305",
  "author": {
    "name": "Apache Magpie",
    "url": "https://magpie.apache.org/"
  },
  "homepage": "https://magpie.apache.org/",
  "repository": "https://github.com/apache/magpie",
  "license": "Apache-2.0",
  "skills": "./skills"
}
Changes

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.

  1. yesterday Changed a4f321a227a9
  2. 4d ago Changed 8ff72289bb86
  3. 6d ago Changed 1a207228279a
  4. 9d ago Changed 42c043661b1c
  5. 10d ago Changed 23b3e1aec6bf
  6. 11d ago Changed d07ab349f362
  7. 13d ago Changed 9b6baecdff2e
  8. 24d ago Changed 39f61ef0e13c
  9. 25d ago Changed aca4d6101a57
  10. 28d ago First seen · 14 lines scan A 0ebe83b2058c

Subscribe to this mod's changes

magpie-security is a plugin published in the GitHub repository apache/magpie (120 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.