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 isolated-setup-verifygit 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/isolated-setup-verify)<a href="https://agentmods.dev/skills/apache/magpie/isolated-setup-verify"><img src="https://agentmods.dev/badge/skills/apache/magpie/isolated-setup-verify/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.
<a href="https://agentmods.dev/skills/apache/magpie/isolated-setup-verify"><img src="https://agentmods.dev/badge/skills/apache/magpie/isolated-setup-verify.svg" alt="Reviewed on agentmods" width="80" 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.00057 | $0.09838 |
| Opus 5.5 | $0.00023 | $0.03935 |
| Sonnet 5.5 | $0.00011 | $0.01968 |
| Haiku 4.5 | $0.00006 | $0.00984 |
Grade D, and why
isolated-setup-verify scanned grade D with 3 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 today.
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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
- **7a — credential files.** For each of `~/.aws/credentials`, the `~/.ssh/id_*` private keys (not `*.pub`), `~/.config/gh/hosts.yml`, `~/.netrc` and `~/.docker/config.json`, run `test -r <path>` and `stat` it (`stat -c Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Evaluate the merge of the project `.claude/settings.json`, the project-local `.claude/settings.local.json`, the user-scope `~/.claude/settings.json` and, where readable, the managed settings (`/etc/claude-code/managed-se Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`permissions.deny` patterns match only the *first* command of a Bash tool call, so a chained `curl` later in the pipeline can slip past on macOS (which has no socat network proxy as a backstop). How it starts
The opening of the file, as written. The whole thing — 338 lines — stays where its author put it; the contents beside it link to each section on GitHub.
setup-isolated-setup-verify
Runtime routing (run before the Claude-specific checks)
Use the operator's explicitly requested runtime when supplied; otherwise use the active session's runtime. An installed executable or configuration directory alone does not select a runtime. For the routing below, treat that selection as the active harness.
When the active harness is Codex, follow the full verification contract in docs/adapters/codex.md, including its hook-trust, vetted-operation and isolation-gap checks. Report every Codex check and then stop. Do not interpret the Claude settings checks below as Codex requirements.
When the selected runtime is Antigravity, follow docs/adapters/antigravity.md: check the user-scope profile, guard registration, skill discovery, and actual runtime behavior. Report static and live checks separately, including any checks not run and the documented isolation limits. Do not require Claude configuration; then stop before the Claude-specific checks below.
When the selected runtime is Pi, follow docs/adapters/pi.md: check that the framework package is installed for the user (not per project), that the Magpie extension loads, and the actual runtime behavior of the guard, the rules and the bash sandbox. Report static and live checks separately, including any checks not run and the documented limits. Do not require Claude configuration; then stop before the Claude-specific checks below.
When the selected runtime is Copilot CLI, follow docs/adapters/copilot.md: check the hook registration and probe an allow, a deny and a silent write.
When the harness is Claude Code, continue with the existing checks below. If the harness cannot be determined, ask once.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed · +43 lines · +3 tokens per session a73d56de3868
- yesterday Changed · +4 lines b068a3b1b4c2
- 3d ago Changed · +31 lines b613af268930
- 5d ago Changed · +1 lines 275c1a91473d
- 10d ago Changed · +13 lines 39961e3c6289
- 11d ago Changed · +7 lines 6691444c5ea3
- 12d ago Changed · +22 lines fd8197a0f549
- 19d ago Changed · +2 lines · +4 tokens per session e44c8ab2aeb5
- 21d ago Changed · +1 lines 7f0138ffcb07
- 22d ago First seen · 214 lines · 50 tokens per session scan D 0f3241b392a9
isolated-setup-verify is a skill published in the GitHub repository apache/magpie (128 stars, last pushed yesterday), licensed Apache-2.0. It adds 57 tokens to every session and 9,838 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it D with 3 findings (reaches for credential files, reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-14.
Other skills, from other repositories
aip-tracker
Track Airflow Improvement Proposal (AIP) implementation progress by comparing Confluence specs against codebase evidence. Use when asked to assess, report on, or compare AIP status.
cyberowlai
Check if recent cybersecurity alerts from 10 international CERTs affect your current project. Use when the user asks about security vulnerabilities, CVEs, "is my project affected", "any new security alerts", "check for vulnerabilities", "cyberowlai", or "/cyberowlai". Also trigger when the user is working on…
vulnerability-db
A practical guide for AI agents that need to use vdb. If you are changing the code rather than using it, read AGENTS.md instead.
bob-update
Check for Hacker Bob package updates and guide project-local update installation from Codex.
bob-export
Create a Hacker Bob post-release improvement bundle for the currently installed Bob version.
wordpress-plugin-hunt
Hunt WP plugins via REST, exploit CVEs when version known.