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 skills add vanducng/skills --skill astro-airflowgit clone --depth 1 https://github.com/vanducng/skillsWrote 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/vanducng/skills/astro-airflow)<a href="https://agentmods.dev/skills/vanducng/skills/astro-airflow"><img src="https://agentmods.dev/badge/skills/vanducng/skills/astro-airflow/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/skills/vanducng/skills/astro-airflow"><img src="https://agentmods.dev/badge/skills/vanducng/skills/astro-airflow.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.00153 | $0.03646 |
| Opus 5 | $0.00077 | $0.01823 |
| Sonnet 5 | $0.00031 | $0.00729 |
| Haiku 4.5 | $0.00015 | $0.00365 |
Grade B, and why
astro-airflow scanned grade B with 2 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 11d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
afw() { curl -fsSL -X "$1" -H "Authorization: Bearer ${ASTRO_TOKEN}" -H "Content-Type: application/json" "${AF_URL}$2" -d "$3"; } Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
description: "Inspect and debug Airflow on Astronomer (Astro) deployments - DAG runs, task logs, container logs, env vars, and deployment state. Use when the user mentions Astro/Astronomer, asks about DAG runs or task lo How it starts
The opening of the file, as written. The whole thing — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
astro-airflow
Read-only debugging surface for Airflow on Astro. Pair three tools:
| Need | Tool |
|---|---|
| DAG runs, task logs, import errors, health, connections, variables, pools | af (Airflow REST wrapper) |
| Container logs, deployment inspect, env vars, hibernate/wake | astro deployment ... |
Local astro dev start / parse / scheduler restart |
vd:managing-astro-local-env |
| Create or edit YAML DAGs | vd:dag-factory |
| User says "use Otto", long audit, Airflow 2→3 upgrade | vd:delegating-to-otto |
| Deep RCA after logs are in hand | vd:debug then vd:fix |
af not installed or no remote instance configured |
curl against /api/v2/ (Airflow 3) or /api/v1/ (Airflow 2) |
When NOT to use: local-only Airflow (astro dev start, parse, pytest) - that is vd:managing-astro-local-env. YAML authoring is vd:dag-factory. This skill is remote (staging/prod) inspection, plus wiring af at those URLs.
Prerequisites
astroCLI ≥ 1.42, logged in (astro login; verify withastro context list)curl+jqafoptional but preferred:uv tool install astro-airflow-mcp(one-shot:uvx --from astro-airflow-mcp af)- A Deployment / Workspace / Organization API token in gopass for curl fallback. Mint via Astro UI → Deployment → Access → API Tokens. Least-privilege:
deployment.get+deployment.airflow.*.get.
Always resolve the live deployment ID first. IDs in project docs go stale.
astro deployment list
astro deployment inspect <deployment-id> --key metadata.airflow_api_url
Choose the interface
- Named Otto / upgrade / long investigation →
vd:delegating-to-otto. afon PATH (oruvx --from astro-airflow-mcp af) and a configured instance → useaf. See references/af.md.- Platform / container logs / env vars →
astro deployment ...below. - Otherwise → curl fallback.
af instance discover creates API tokens in Astro Cloud. Always --dry-run first and get explicit approval before a real discover.
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.
- 11d ago First seen · 282 lines · 153 tokens per session scan B e6cb4760f22b
astro-airflow is a skill published in the GitHub repository vanducng/skills (7 stars, last pushed yesterday), licensed MIT. It adds 153 tokens to every session and 3,646 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
error-translator
A Chinese-language assistant that translates English programming errors and explains what they mean. It covers common errors from languages and frameworks including Python, JavaScript, TypeScript, Java, and others.
eslint-fix
A project-aware assistant for finding and fixing ESLint errors, warnings, and configuration compatibility problems. ESLint is a tool that checks JavaScript and TypeScript code for style and common mistakes.
perf-profiler
A performance investigation guide that uses repeatable measurements and profiling evidence to find where software spends time or resources. Profiling records runtime activity such as CPU use, memory use, database work, or network delays.
log-analyzer
A log-analysis helper that reads application and system logs to find unusual patterns and likely causes. Logs are records of events such as errors, requests, warnings, and service activity.
audit
Project-wide health audit pipeline that fans out to all analysis skills in parallel, evaluates findings, and produces a unified report at .turbo/audit.md. Use when the user asks to "audit the project", "run a full audit", "project health check", "audit my code", "codebase audit", or "comprehensive review".
investigate
Systematically investigate bugs, test failures, build errors, performance issues, or unexpected behavior by cycling through characterize-isolate-hypothesize-test steps. Use when the user asks to "investigate this bug", "debug this", "figure out why this fails", "find the root cause", "why is this broken"…