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-stale-sweepnpx skills add apache/magpie --skill issue-stale-sweepgit 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/issue-stale-sweep)<a href="https://agentmods.dev/skills/apache/magpie/issue-stale-sweep"><img src="https://agentmods.dev/badge/skills/apache/magpie/issue-stale-sweep.svg" alt="Measured on agentmods" 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 | $0.00080 | $0.05853 |
| Opus 5 | $0.00040 | $0.02926 |
| Sonnet 5 | $0.00016 | $0.01171 |
| Haiku 4.5 | $0.00008 | $0.00585 |
Grade A, and why
magpie-issue-stale-sweep 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 4d 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 — 532 lines — stays where its author put it; the contents beside it link to each section on GitHub.
issue-stale-sweep
This skill is the stale-issue sweep for the project's general issue
tracker. It identifies open issues that have had no new comment or update
activity past a configurable inactivity threshold, classifies each as
either REQUEST-UPDATE or CLOSE-STALE, and — on the user's explicit
confirmation — posts one lightweight comment per issue (a nudge or a
pre-close notice, as appropriate).
The skill never closes, labels, transitions, or edits any tracker field without confirmation. The decision belongs to the maintainer; this skill surfaces the candidates and pre-drafts the comments so the maintainer can review in bulk and confirm or skip individually.
It composes with:
issue-triage— the main triage skill for unsorted-new issues; stale-sweep is the hygiene pass for the open-but- dormant pool.issue-reassess— for the resolved / EOL pool (stale-sweep handles the still-open dormant pool instead).
Disposition vocabulary
The skill uses exactly two disposition classes:
| Class | When to propose | Follow-up action |
|---|---|---|
REQUEST-UPDATE |
Issue is dormant past the warn threshold but not yet past the close threshold; reporter has not recently responded | Post a nudge comment asking the reporter to confirm the issue is still relevant on the current <default-branch>; no state change yet |
CLOSE-STALE |
Issue is dormant past the close threshold and has already received a REQUEST-UPDATE nudge with no response, or is dormant past a hard-close threshold with no nudge needed |
Post a pre-close notice and, on a second explicit confirmation, close the issue |
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.
- 4d ago First seen · 532 lines · 80 tokens per session scan A 009571d8be27
magpie-issue-stale-sweep is a skill published in the GitHub repository apache/magpie (87 stars, last pushed 2d ago), licensed Apache-2.0. It adds 80 tokens to every session and 5,853 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
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…
upgrade-fab-provider
Upgrade the pinned Flask-AppBuilder (FAB) dependency in the Apache Airflow FAB provider (providers/fab/). Bumps the exact flask-appbuilder== pin and its mirror constant, regenerates uv.lock, drives the testfabalignment.py drift tripwire, reviews the vendored security-manager override.py against the new upstream FAB…
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-new-sdk
Guide for implementing a brand-new language SDK for Airflow (AIP-108). Use this skill when a contributor wants to add support for a new programming language — designing the Python coordinator, implementing the wire protocol in the target language, writing the bundle format, and structuring the PR. Trigger on phrases…
airflow-java-sdk
Guide for contributing to the Airflow Java SDK (AIP-108). Use this skill whenever a contributor is working in the java-sdk/ directory or on the Java coordinator in task-sdk/src/airflow/sdk/coordinators/java/ — whether they want to add a feature, write tests, fix a bug, understand the architecture, or prepare a PR.…
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.