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/lee-w/maigo/airflow-awarenpx skills add Lee-W/maigo --skill airflow-awaregit clone --depth 1 https://github.com/Lee-W/maigoWrote 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/lee-w/maigo/airflow-aware)<a href="https://agentmods.dev/skills/lee-w/maigo/airflow-aware"><img src="https://agentmods.dev/badge/skills/lee-w/maigo/airflow-aware.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.1 | $0.00081 | $0.06894 |
| Opus 5 | $0.00041 | $0.03447 |
| Sonnet 5 | $0.00016 | $0.01379 |
| Haiku 4.5 | $0.00008 | $0.00689 |
Grade A, and why
airflow-aware 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 2d 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 — 497 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Airflow-Aware
Loaded by: repo-detect hook (SessionStart) when apache/airflow is detected in git remote or file structure.
Applies to: Any skill execution within an Apache Airflow contributor checkout — review, quick-fix, refactoring, or otherwise.
When to apply
This is a knowledge layer, not a review checklist.
It is loaded automatically by the
repo_detect hook
at session start when an Apache Airflow repo is detected.
It mirrors and supplements the repo's own AGENTS.md / CLAUDE.md, condensed for agent context.
It can also be triggered manually via a memory entry with triggers: [airflow-aware]
(see Memory-triggered skill loading).
Once loaded, treat every convention as background — do not re-read each task.
Contributor conventions
1. Read AGENTS.md first — it wins
The single source of truth for contributor conventions lives in the repo itself. This skill is a condensed onramp formatted for agent startup context, not a competing authority.
- First action: read
AGENTS.md(orCLAUDE.md— both are identical, 455 lines). - Conflict resolution: if anything in this skill contradicts
AGENTS.md, the repo file wins. - Review tasks: also read
.github/instructions/code-review.instructions.mdfor review-specific guidance.
2. Naming — Dag (prose) vs DAG (code)
In prose, write Dag (title case) — never all-caps DAG unless referring to the Python
class, and never expand "Directed Acyclic Graph". Code tokens stay as-is: class DAG,
dag_id, airflow dags list, dag_processing/, DAG_FOLDER. See the "Naming" section of
AGENTS.md when in doubt.
Naming hook false positives
What ships with it
5 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.
- 2d ago Changed · +9 lines 73140cb26ff4
- 6d ago First seen · 488 lines · 81 tokens per session scan A ff3228c400bd
airflow-aware is a skill published in the GitHub repository Lee-W/maigo (14 stars, last pushed 3d ago), licensed MIT. It adds 81 tokens to every session and 6,894 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…