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-reassessnpx skills add apache/magpie --skill issue-reassessgit 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.00096 | $0.05092 |
| Opus 5 | $0.00048 | $0.02546 |
| Sonnet 5 | $0.00019 | $0.01018 |
| Haiku 4.5 | $0.00010 | $0.00509 |
Grade A, and why
magpie-issue-reassess 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 3d 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 — 467 lines — stays where its author put it; the contents beside it link to each section on GitHub.
issue-reassess
Use this skill when the task is a campaign over a bounded set
of resolved or end-of-life <issue-tracker> issues: pick the
candidate set, run each reporter's reproducer against
<default-branch> via issue-reproducer,
classify the outcome, attach a nature analysis, and produce a report
a maintainer can scan and act on. The campaign is read-only against
the tracker; the output is advisory.
This skill is the campaign layer. Per-issue mechanics live in sibling skills:
issue-reproducer— the load-bearing per-issue piece: locate the reproducer, classify the shape, adapt, run, record evidence asverdict.json. This skill calls into it for every candidate.issue-triage— sibling for the unsorted-new pool (this skill handles resolved / EOL / reopened pools instead).issue-fix-workflow— where thestill-fails-*tail goes once the campaign is done; the campaign produces ready-made reproducers for the fix flow.issue-reassess-stats— read-only dashboard over the campaign artefacts this skill produces.
Golden rules
What ships with it
3 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.
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.
- 3d ago First seen · 467 lines · 96 tokens per session scan A 0120a8bbd5ef
magpie-issue-reassess is a skill published in the GitHub repository apache/magpie (84 stars, last pushed 3d ago), licensed Apache-2.0. It adds 96 tokens to every session and 5,092 once invoked, about $0.0005 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
prepare-providers-documentation
Replace the manual commit-by-commit classification step in breeze release-management prepare-provider-documentation with AI-driven classification. For each provider with pending changes, analyze every PR (batched into one sub-agent per provider, not one per PR), pay special attention to potentially breaking changes by…
magpie-setup
Adopt and maintain the apache-magpie framework in a project repo via the snapshot-based adoption mechanism. The only framework skill committed in an adopter's repo; every other skill is a symlink the adopt sub-action wires up. Sub-actions: /magpie-setup - first-time adoption (default; main-checkout only) /magpie-setup…
aip-user-stories
Generate verified recipe playbooks from AIPs with PR implementations (post mode), or speculative user stories from AIPs without implementations (pre mode). Use when the user provides an AIP URL or AIP content, optionally with PR URLs and file paths.
airflow-translations
Add or update translations for the Apache Airflow UI. Guides through setting up locales, scaffolding translation files, translating with locale-specific guidelines, and validating results. Use when working with i18n tasks in airflow-core/src/airflow/ui/public/i18n/locales/.
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.
Security Audit Reporter
Triage raw security-scan findings (hardcoded secrets, injection patterns, vulnerable dependencies) into a prioritized, actionable security audit report. Use for security audit, code audit, vulnerability triage, and risk review.