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.03238 |
| Opus 5.5 | $0.00061 | $0.01295 |
| Sonnet 5.5 | $0.00031 | $0.00648 |
| Haiku 4.5 | $0.00015 | $0.00324 |
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 1mo 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 — 246 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) |
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.
uvx --from astro-airflow-mcp af instance list
uvx --from astro-airflow-mcp af instance discover --dry-run
# only after the user says yes:
# uvx --from astro-airflow-mcp af instance discover astro
uvx --from astro-airflow-mcp af instance use <name>
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.
- 1mo ago Changed · +18 lines 2181920b970e
- 1mo ago Changed · -54 lines b2b70841c284
- 1mo ago First seen · 282 lines · 153 tokens per session scan B e6cb4760f22b
astro-airflow is a skill published in the GitHub repository vanducng/skills (8 stars, last pushed today), licensed MIT. It adds 153 tokens to every session and 3,238 once invoked, about $0.0006 per session on Opus 5.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
observability-baseline
Scaffold-time observability so a shipped product is not blind in prod from day one — error capture (Sentry), request-id structured logging, and /healthz + /readyz endpoints. stack-baseline pins Sentry but nothing wires it; this is the wiring. Loaded by app-scaffolder (bake into the scaffold), infra-provisioner (prod…
swc-plugin-compatibility
Diagnose and fix Lingui SWC plugin compatibility errors with Next.js, Vite, Rspack, or other SWC runtimes. Use when seeing errors like "failed to invoke plugin", "failed to run Wasm plugin transform", "Failed to deserialize program received from host", "Failed to execute SWC plugin", "out of bounds memory access", or…
interactive-debugging
Use this skill when debugging runtime behavior requires live data from the running app, temporary instrumentation, or hypothesis verification through logs. Trigger for async timeouts, stale or incorrect state updates, race conditions, event ordering bugs, intermittent failures, browser/client behavior that static…
observability-and-instrumentation
Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.
mirrord-up
Helps users run multiple concurrent mirrord sessions from a single mirrord-up.yaml (compose-style multi-service local debugging). Use when the user mentions mirrord up, mirrord-up.yaml, mirrord up init, debugging several related microservices together, or managing multiple mirrord sessions' lifecycle in one command.
diag-k8s-pod-crashloop
A diagnostic runbook for Kubernetes Pods stuck in CrashLoopBackOff. A Pod is a Kubernetes unit that runs one or more containers; CrashLoopBackOff means a container keeps failing and Kubernetes waits longer between restart attempts.