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 agentmods add skills/apache/magpie/issue-triagenpx skills add apache/magpie --skill issue-triagegit clone --depth 1 https://github.com/apache/magpieWhat 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 | $0.00080 | $0.07958 |
| Opus 5 | $0.00040 | $0.03979 |
| Sonnet 5 | $0.00016 | $0.01592 |
| Haiku 4.5 | $0.00008 | $0.00796 |
Grade A, and why
magpie-issue-triage 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.
How it starts
The opening of the file, as written. The whole thing — 749 lines — stays where its author put it; the contents beside it link to each section on GitHub.
issue-triage
This skill is the initial-triage discussion-starter for issues on the project's general issue tracker. For each open issue in the configured candidate pool, it reads the issue body and comments, applies the project's triage criteria, classifies the candidate disposition, and — on the user's explicit confirmation — posts a triage-proposal comment that invites the project team to react.
The skill never transitions workflow state, never closes, never assigns, never edits any tracker field. The disposition decision belongs to team consensus; this skill opens the discussion that produces it, and sibling skills apply the state change once consensus lands.
It composes with:
issue-reproducer— invoke when the classification depends on whether the reporter's code still fails on<default-branch>.issue-fix-workflow— invoke by hand after the team agrees a triaged issue is a confirmed bug or feature ready to fix.issue-reassess— sibling for sweep-mode work on the resolved or end-of-life pool (this skill handles the unsorted-new pool).
Golden rules
Golden rule 1 — read-only on tracker state. This skill posts discussion comments and nothing else. No workflow transitions, no label mutations, no body edits, no project-board column moves, no field changes. The skill's output is text on the tracker that invites reaction; the team's reply drives state change, applied later by sibling 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 · 749 lines · 80 tokens per session scan A 2b36c805a7fb
magpie-issue-triage is a skill published in the GitHub repository apache/magpie (84 stars, last pushed 3d ago), licensed Apache-2.0. It adds 80 tokens to every session and 7,958 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-08-30.
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.
omv
Skill "omv" from bx33661/oh-my-vul, covering omv, commands, skills in this collection, registry and state directory.
paperclip
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
setup-matt-pocock-skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
github-labels-query
List GitHub repository labels with perpage pagination and name filtering support.