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.
/plugin marketplace add apache/magpienpx agentmods add plugins/apache/magpie/magpie-pairinggit clone --depth 1 https://github.com/apache/magpieGrade A, and why
magpie-pairing 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 2d 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.
What it actually says
{
"name": "magpie-pairing",
"description": "Apache Magpie \u2014 pair a change with a structured self-review or a multi-agent adversarial review.",
"version": "0.2.0.dev0",
"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"
}
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.
- 2d ago First seen · 14 lines scan A 6f2c95d3b2e7
magpie-pairing is a plugin published in the GitHub repository apache/magpie (84 stars, last pushed 2d ago), 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.
Other plugins, from other repositories
dep-diff
Translates a lockfile diff into a human-readable upgrade plan for npm and PyPI.
nist-nvd-mcp-server
Search and audit CVEs by keyword, severity, CWE, CISA KEV status, and CPE via the NIST National Vulnerability Database. STDIO or Streamable HTTP.
find-cve-agent
CVE hunting harness for open source security research. A 5-agent team that systematically finds, validates, and reports real vulnerabilities in open source packages.
tridentchain-security
Comprehensive local supply-chain CVE scanning — project deps, system packages (Homebrew/apt), AND IDE extensions (VS Code, JetBrains) — with EPSS exploit-probability and CISA KEV prioritisation. Includes validate-after-patch workflow to confirm fixes. Local-first; no source code leaves the user's machine. Complements…
threat-intel-marketplace
A single-plugin marketplace hosting the Threat Intel Toolkit — defensive IOC triage on free, key-free open-source threat feeds.
threat-intel-toolkit
Defensive IOC + vulnerability triage on free/open-source intel: a subagent plus two skills — threat-intel-lookup (aggregates 10 key-free feeds and looks up IPs, domains, URLs, CVEs) and exploit-availability-check (rates a CVE's exploit/PoC maturity via KEV, EPSS, Metasploit, Nuclei, Exploit-DB, and PoC aggregators).…