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-user-storiesnpx skills add apache/airflow --skill aip-user-storiesgit clone --depth 1 https://github.com/apache/airflowWrote 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/airflow/aip-user-stories)<a href="https://agentmods.dev/skills/apache/airflow/aip-user-stories"><img src="https://agentmods.dev/badge/skills/apache/airflow/aip-user-stories.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.00056 | $0.02278 |
| Opus 5 | $0.00028 | $0.01139 |
| Sonnet 5 | $0.00011 | $0.00456 |
| Haiku 4.5 | $0.00006 | $0.00228 |
Grade A, and why
aip-user-stories 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AIP-to-User-Stories Playbook
Invocation
/aip-user-stories <AIP-URL-or-pasted-content> [<PR-URL>...] [<file>...]
If no arguments: print this usage synopsis and stop.
Mode Detection
An argument starting with https://cwiki.apache.org/confluence/ is the AIP URL. Arguments starting with https://github.com/apache/airflow/pull/ are PR URLs. Other arguments are local file paths.
- PR URLs present → post-implementation mode: generates verified recipe playbooks from actual code.
- No PR URLs → pre-implementation mode: generates speculative user stories to help AIP authors validate design.
PR URLs signal post mode and serve as discovery hints — starting points for finding the implementation in the codebase. They are not an exhaustive list of all PRs for the feature, and the skill must explore beyond the supplied PRs to find the full implementation.
AIP Number
Extract the AIP number from the URL path (e.g., AIP-76 from a URL containing /aip-76 or /AIP-76). If the number cannot be determined from the URL or pasted content, ask the user.
Output Path
Write the final playbook to .claude/aip-{number}.md where {number} is the extracted AIP number. If the file already exists, ask the user before overwriting.
Post-Implementation Mode
Source of truth: the actual implementation in the codebase and PRs — not the AIP specification. When the AIP proposes APIs that differ from what was implemented, the playbook follows the implementation.
Phase 1 — Parse
Separate arguments into:
- AIP source: a URL to fetch, or pasted content already in the conversation.
- PR URLs: GitHub pull request URLs (one or more).
- File paths: local files (example Dags, source files, tests).
AIP content can come from a URL (fetched via WebFetch) or pasted directly by the user — both are equally valid input paths. If a URL fetch returns empty or garbled content, tell the user and ask them to paste the AIP content instead.
What ships with it
1 file 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 · 210 lines · 56 tokens per session scan A ccabfb68f9dd
aip-user-stories is a skill published in the GitHub repository apache/airflow (46,687 stars, last pushed yesterday), licensed Apache-2.0. It adds 56 tokens to every session and 2,278 once invoked, about $0.0003 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.
airflow-expert
Expert-level Apache Airflow orchestration, DAGs, operators, sensors, XComs, task dependencies, and scheduling.
apache-airflow-orchestration
Complete guide for Apache Airflow orchestration including DAGs, operators, sensors, XComs, task dependencies, dynamic workflows, and production deployment.
airflow-dag-orchestrator
Apache Airflow DAGs, operators, SLA monitoring, and workflow orchestration. Activate on: Airflow, DAG, operator, sensor, scheduler, task dependency, SLA, backfill, XCom. NOT for: dbt transformations (use dbt-analytics-engineer), streaming pipelines (use streaming-pipeline-architect).
airflow
Apache Airflow workflow orchestration reference. Covers DAG authoring (TaskFlow API + classic), operators, sensors, connections, XComs, deployment (Docker, Kubernetes, Helm), testing, and common patterns including dynamic task mapping and data-aware scheduling.
airflow-dag-patterns-v2
Apache Airflow DAG Patterns workflow skill. Use this skill when the user needs Build production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. Use when creating data pipelines, orchestrating workflows, or scheduling batch jobs and the operator should preserve the upstream…