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/airflow/aip-trackernpx skills add apache/airflow --skill aip-trackergit clone --depth 1 https://github.com/apache/airflowWhat 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.00041 | $0.01305 |
| Opus 5 | $0.00020 | $0.00652 |
| Sonnet 5 | $0.00008 | $0.00261 |
| Haiku 4.5 | $0.00004 | $0.00130 |
Grade A, and why
aip-tracker 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 yesterday.
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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AIP Progress Tracker Skill
Assess implementation progress of Airflow Improvement Proposals by comparing what the Confluence spec promises against what the codebase delivers.
When to Use This Skill
Use this skill when the task involves:
- Tracking AIP implementation status
- Comparing a spec against shipped code
- Producing a cross-AIP progress report
Available Tools
You have access to these tools for gathering evidence:
fetch_confluence_page(page_id)-- fetch an AIP spec from Confluencesearch_github_prs(query)-- search GitHub PRs/commits for an AIPget_repo_file_tree(path_prefix)-- list files under a directory in the repo
Evidence Gathering Strategy
For each AIP, gather evidence from all three sources before assessing:
- Confluence spec -- call
fetch_confluence_pagewith the AIP's page ID. Extract: deliverables, phases, completion criteria, and status. - GitHub PRs and commits -- call
search_github_prswith both the AIP number (e.g. "AIP-76") AND topic keywords (e.g. "asset partition"). Deduplicate results. - Codebase file tree -- call
get_repo_file_treewith the AIP's known directory prefixes. Count source files and test files.
Deliverable Extraction
Extract deliverables from the specification's own structure. Use these sources in priority order:
- Numbered completion criteria (e.g. "Definition of Done", "Completion Criteria") -- each numbered item is one deliverable.
- Phase definitions -- each bullet or item under a phase heading is one deliverable.
- Explicitly enumerated components (classes, operators, API endpoints, CLI commands, UI features) listed in the spec.
Critical: Do NOT split a single spec item into multiple deliverables (e.g. do not count individual files within one component as separate deliverables). Do NOT merge multiple spec items into one. Use the spec's own granularity -- if the spec says "partition mappers" as one item, that is one deliverable, not five separate file-level deliverables.
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.
- yesterday First seen · 144 lines · 41 tokens per session scan A 8596094d3990
aip-tracker is a skill published in the GitHub repository apache/airflow (46,647 stars, last pushed yesterday), licensed Apache-2.0. It adds 41 tokens to every session and 1,305 once invoked, about $0.0002 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
airflow-workflow
Execution guide for Airflow scheduled jobs — troubleshooting, updating, connid conventions, and cron references.
dagster-docs
Expert guidance for writing documentation for the Dagster docs website. ALWAYS use before creating or updating documentation in the docs directory.
git-workflow
Git operations: commits, branches, PRs, and conflict resolution.
jamjet-durability-patterns
Production durability patterns for AI agents on the JVM — crash recovery, audit trails, human-in-the-loop, and replay testing using JamJet runtime.
bugsweep
Systematic bug sweep with a codebase-scaled target value, doubling escalation, area tracking, and final verification. Use on /bugsweep or whenever the user requests a systematic bug pass.
compare-race
Use when the user wants to send the same prompt to several LLMs and compare the answers - sequentially (stopwatch, clean per-lane timing) or in parallel (true race), with optional repetitions per model, judged by the starting model across quality, correctness, completeness, instruction fidelity and latency (time is…