triage

triage is a skill for Claude Code from apache/magpie. It costs 75 tokens per session (5,300 once invoked), scanned A, a copy of issue-triage, Apache-2.0.

An issue classification tool for open project issues. It reads the issue and its comments, assigns a proposed outcome, and can prepare a comment for the team to review.

In plain words
What is it for?
Use it to assess a set of open issues and draft triage proposals for the project team.
Why use it?
It helps teams sort incoming work without immediately changing labels, status, or other tracker data. Posting requires user confirmation.

Skill for Claude Code ✓ vendor

Written for Claude Code: when-to-use in frontmatter. Also seen: mentions subagents; mentions AGENTS.md.

Part of the magpie-issue plugin — 8 skills shipped together

Good fit Use it to assess a set of open issues and draft triage proposals for the project team.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/apache/magpie/triage
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.

Any agent
npx skills add apache/magpie --skill triage
Clone the repo
git clone --depth 1 https://github.com/apache/magpie

Made for: Claude Code.

Or install magpie-issue, the plugin that ships this one along with the rest of its 8 skills.

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 triage

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/apache/magpie/triage"><img src="https://agentmods.dev/badge/skills/apache/magpie/triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,300 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 88% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00075 $0.05300
Opus 5.5 $0.00030 $0.02120
Sonnet 5.5 $0.00015 $0.01060
Haiku 4.5 $0.00007 $0.00530

Measured 5d ago against content hash 849599c851a2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 5d 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.

Origin

This is a copy

88% identical to issue-triage — 524 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/magpie-issue/skills/triage/SKILL.md · 496 lines

How it starts

The opening of the file, as written. The whole thing — 496 lines — stays where its author put it; the contents beside it link to each section on GitHub.

issue-triage

Pre-flight — is this project set up?

Do this first, before anything else in this skill, and do it silently. One command answers it and carries its own rules; there is nothing else to read.

Run the checker with this skill's own frontmatter name: and surface_hash:, and one --requires for each requires_config: entry:

PYTHONPATH=".apache-magpie-local:$(git rev-parse --git-common-dir)/../.apache-magpie-local:$(git rev-parse --git-common-dir)/apache-magpie" \
  python3 -m setup_preflight --skill <name> --hash <surface_hash> [--requires <file>]...

The path finds the checker /magpie-setup:setup config installed in the personal layer: this checkout's .apache-magpie-local/, the main checkout's when this is a linked worktree, or the git directory's apache-magpie/ when Magpie is only installed.

  • {"verdict": "ok"} → silent. Continue into the work the user asked for and say nothing about pre-flight. This is the ordinary answer.
  • {"verdict": "action", ...} → each finding names a section, and rules carries that section's text. Follow it. The facts are the inputs; what to propose, and what may not be done, are in the rules rather than here. Act on a finding only through its rules.
  • The command did not run at all — no such module, a non-zero exit, no python3 — → never read that as a pass, and do not re-derive the check by hand: it lives in code so that there is one version of it. If the project has no .apache-magpie.lock, .apache-magpie-overrides/, or personal layer (any of the three directories above), nothing has been set up here and there is nothing to reconcile — resolve this skill's requires_config: entries yourself (first match wins: .apache-magpie-local/<file>, the main checkout's .apache-magpie-local/<file>, <git-common-dir>/apache-magpie/<file>, then .apache-magpie-overrides/<file>), stay silent if they all resolve, and run /magpie-setup:setup config for this skill if any does not, which also installs the checker. Otherwise the project is set up and its checker is missing or stale: say so, propose /magpie-setup:setup config to install it or /magpie-setup:setup upgrade to refresh it, and carry on with the work.

Read the full file on GitHub · 496 lines

Files

What ships with it

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

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. 5d ago Changed · +2 lines 849599c851a2
  2. 15d ago Changed · +14 lines 5919b7223d36
  3. 21d ago Changed · -15 lines e052dd28ec1a
  4. 23d ago Changed · -304 lines 51478f2b4bf5
  5. 24d ago Changed · +1 lines c5f8d05ec72f
  6. 27d ago Changed · -5 tokens per session 170b5d201174
  7. 28d ago Changed · -94 lines 4bfd7cf06e67
  8. 1mo ago Changed · +33 lines 4f2d616a84a0
  9. 1mo ago First seen · 859 lines · 80 tokens per session scan A ecf7f50054a9

Subscribe to this mod's changes

triage is a skill published in the GitHub repository apache/magpie (120 stars, last pushed today), licensed Apache-2.0. It adds 75 tokens to every session and 5,300 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to issue-triage, differing in 524 lines, and is treated as a copy.