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 fmind/dot --skill airflowgit clone --depth 1 https://github.com/fmind/dotWrote 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/fmind/dot/airflow)<a href="https://agentmods.dev/skills/fmind/dot/airflow"><img src="https://agentmods.dev/badge/skills/fmind/dot/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/fmind/dot/airflow"><img src="https://agentmods.dev/badge/skills/fmind/dot/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.00018 | $0.00922 |
| Opus 5.5 | $0.00007 | $0.00369 |
| Sonnet 5.5 | $0.00004 | $0.00184 |
| Haiku 4.5 | $0.00002 | $0.00092 |
Grade A, and why
airflow 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 8d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apache Airflow with Astronomer CLI
Use astro for local Apache Airflow development, DAG authoring, task testing, and debugging. python-stack owns Python package conventions and docker manages container runtimes.
Docker mode (the default) needs an existing Docker-compatible engine; run dot doctor --headroom before the first image pull or build. --standalone runs Airflow on the host without Docker. Workstation tools disable anonymous telemetry (ASTRO_TELEMETRY_DISABLED=1). Inspect the project's Airflow version before choosing service flags (--api-server and --dag-processor for Airflow 3; --webserver for Airflow 2).
Workflow
-
Start local environment:
--no-browserkeeps the UI from opening.astro dev start --no-browser -
Validate DAG syntax and integrity: parse DAG files to catch import and configuration errors without waiting for the scheduler.
astro dev parse -
Test tasks and runs: execute unit tests or run individual tasks directly inside the local environment.
astro dev pytest astro dev run tasks test <dag_id> <task_id> -
Inspect service and task logs: select the relevant component and keep
--followopt-in.astro dev logs --scheduler astro dev logs --api-server -
Stop or rebuild environment: stop containers when done or rebuild when changing dependencies in
requirements.txt.astro dev stop # After changing requirements.txt or Dockerfile: astro dev restart
Gotchas
- Author Airflow 3 DAGs with
airflow.sdk: importdag,task, andDAGfromairflow.sdk;ruff check --select AIR3flags removed and deprecated Airflow 2 imports beforeastro dev upgrade-test. - Proxy URLs replace fixed ports: by default a shared reverse proxy serves each project at
http://<project>.localhost:6563on random backend ports;astro dev proxy statuslists each project's URL and Postgres port.--no-proxyrestores fixed ports (8080for the API server or webserver,5432for Postgres), which can collide with local services. - Task tests record no state:
astro dev run tasks testruns a single task without recording state in the Airflow database; upstream task dependencies must be handled or mocked. - Run upgrade-test before upgrading: before moving to a newer Airflow or Astro Runtime (including Airflow 2 to 3), run
astro dev upgrade-test(optionally--airflow-version <version>); it reports dependency changes, DAG import errors, and deprecation lint without modifying the project.
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.
- 8d ago Changed · -2 lines 2b5e9a209688
- 10d ago Changed fb5fa10904d9
- 11d ago Changed · -3 lines · -1 tokens per session cf1425268893
- 13d ago Changed c373b5b8bce5
- 19d ago Changed 68d681329514
- 27d ago Changed 73a247bd58f9
- 29d ago First seen · 76 lines · 19 tokens per session scan A 43624df318fa
airflow is a skill published in the GitHub repository fmind/dot (11 stars, last pushed 2d ago), licensed MIT. It adds 18 tokens to every session and 922 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-09-17.
Other skills, from other repositories
codecov
Query Codecov for flaky-test signal, failure history, and coverage data via the codecov-api wrapper. Use when asked about flaky tests, intermittent test failures, why a test is failing, coverage on a PR/file/branch, or whenever browser access to Codecov is blocked by the login wall.
k8s-local
Create and manage local Kubernetes clusters (k3d or kind) and deploy to them with kubectl, helm, helmfile, and skaffold. Use for local k8s cluster setup, dev loops, and debugging.
cloud-run
Deploy container services to Google Cloud Run with Artifact Registry, keyless CI identity, Secret Manager, ko, or Dockerfiles.
mise
Configure pinned mise tools and canonical install, format, check, test, build, and watch tasks shared by hooks and CI.
security-scan
Scan repositories with Trivy and gitleaks for vulnerabilities, IaC, secrets, licenses, images, and git history; triage concrete findings.
containerize
Build minimal, non-root OCI images — ko for Go or a distroless multi-stage Dockerfile — then scan, sign, and SBOM them. Use when containerizing or packaging an app for deployment.