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.
git clone --depth 1 https://github.com/astronomer/agentsWrote 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/commands/astronomer/agents/check-airflow-compat)<a href="https://agentmods.dev/commands/astronomer/agents/check-airflow-compat"><img src="https://agentmods.dev/badge/commands/astronomer/agents/check-airflow-compat/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/astronomer/agents/check-airflow-compat"><img src="https://agentmods.dev/badge/commands/astronomer/agents/check-airflow-compat.svg" alt="Reviewed on agentmods" width="80" 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.00014 | $0.00229 |
| Opus 5.5 | $0.00006 | $0.00092 |
| Sonnet 5.5 | $0.00003 | $0.00046 |
| Haiku 4.5 | $0.00001 | $0.00023 |
Grade A, and why
check-airflow-compat 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 2mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- check-airflow-compat — 100% identical, 0 lines differ
What it actually says
Check if recent code changes are compatible with both Airflow versions.
Check for Issues
-
Look for hardcoded API paths outside adapters: !
grep -rn "api/v1\|api/v2" src/astro_airflow_mcp/*.py | grep -v adapters -
Check field normalization in adapters: !
grep -n "execution_date\|logical_date\|datasets\|assets" src/astro_airflow_mcp/adapters/*.py
Key Differences
| Airflow 2.x | Airflow 3.x |
|---|---|
/api/v1 |
/api/v2 |
execution_date |
logical_date |
datasets |
assets |
| Basic auth | OAuth2/JWT |
Run Tests
make test
make test-integration-v2
make test-integration-v3
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.
- 2mo ago First seen · 32 lines · 14 tokens per session scan A 26df0152ec35
check-airflow-compat is a command published in the GitHub repository astronomer/agents (459 stars, last pushed 2d ago), licensed Apache-2.0. It adds 14 tokens to every session and 229 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
devkit.github.review-pr
Provides comprehensive GitHub pull request review with code quality, security, and best practices analysis. Use when reviewing a PR before merging.
devkit.typescript.code-review
Provides comprehensive TypeScript monorepo code review for Nx workspaces including NestJS backend, React web, and React Native mobile apps. Use when reviewing architecture, boundaries, security, performance, CI/CD and Nx-specific practices.
OPSX: Archive
Archive a completed change in the experimental workflow.
speckit.git.remote
Detect Git remote URL for GitHub integration.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.