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 astronomer/agents --skill migrating-dagster-to-airflowgit 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/skills/astronomer/agents/migrating-dagster-to-airflow)<a href="https://agentmods.dev/skills/astronomer/agents/migrating-dagster-to-airflow"><img src="https://agentmods.dev/badge/skills/astronomer/agents/migrating-dagster-to-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/astronomer/agents/migrating-dagster-to-airflow"><img src="https://agentmods.dev/badge/skills/astronomer/agents/migrating-dagster-to-airflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00125 | $0.03401 |
| Opus 5 | $0.00063 | $0.01700 |
| Sonnet 5 | $0.00025 | $0.00680 |
| Haiku 4.5 | $0.00013 | $0.00340 |
Grade A, and why
migrating-dagster-to-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 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.
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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dagster → Airflow 3 (Astro) migration
Migrate a Dagster project to Airflow 3 on Astro Runtime, honestly. The migration is asset-first (Dagster asset graphs translate to Airflow assets and asset-aware schedules, not flattened DAGs), incremental (domain by domain, Dagster stays authoritative until parity), and honest (every definition gets an explicit disposition; semantic deltas are documented, never papered over).
First time driving this? Read reference/quickstart.md first: hour-one commands, the glossary, and what can and cannot break.
Migration at a glance
- Baseline the source project's tests, then inventory it read-only (
scripts/inventory.py→ manifest). - Review classifications (MECH/JUDG/REDESIGN/NONE per
reference/mapping.md); make the go/no-go call (three outcomes; migrate-with-conditions is the common case, stay is the narrow one); plan DAG boundaries, per-edge IO decisions, and Gate 3 expectations into the manifest. - Trial-migrate 2-3 representative units end-to-end through every validation gate.
- Migrate domain by domain through the six-gate ladder (
reference/validation.md), tracking per-unit state (scripts/status.py); fix failure classes viareference/troubleshooting.md, never stub. - Map the platform layer (secrets, alerts, CI/CD, Deployments) per
reference/astro-deployment.md. - Run side by side, then cut over per domain (consumers unpause first; see the checklist), keeping rollback one step away.
- Deliver the migration report: every definition dispositioned, an equivalence row per trigger, losses stated plainly.
Version drift
Verified against Airflow 3.3.0 / Astro Runtime 3.3-2 / astronomer-cosmos 1.15 / Dagster 1.13 (2026-07). Version-sensitive rows in the references carry their floor (notably the 3.2-vs-3.3 partition surface). Before relying on a version-gated claim: check the target (airflow version, astro deployment inspect), probe imports for sdk surface (python3 -c "from airflow.sdk import X"), and prefer --help / API spec discovery over assuming verbatim CLI/REST contracts on newer versions. Playbook entries are version-scoped per entry.
What ships with it
22 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.
- README.md 4.1 KB
- reference/assets.md 5.1 KB
- reference/astro-deployment.md 12 KB
- reference/automation.md 12 KB
- reference/components.md 5.2 KB
- reference/dbt.md 26 KB
- reference/io-and-data-passing.md 10 KB
- reference/mapping.md 25 KB
- reference/partitions.md 12 KB
- reference/quickstart.md 5.3 KB
- reference/troubleshooting.md 16 KB
- reference/validation.md 17 KB
- scripts/inventory.py 43 KB runs code
- scripts/pyproject.toml 653 B
- scripts/status.py 15 KB runs code
- scripts/tests/conftest.py 3.8 KB runs code
- scripts/tests/test_inventory.py 6.0 KB runs code
- scripts/tests/test_merge.py 4.5 KB runs code
- scripts/tests/test_status.py 4.6 KB runs code
- scripts/tests/test_validate_dag.py 4.5 KB runs code
- scripts/uv.lock 24 KB
- scripts/validate_dag.py 19 KB runs code
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 · 149 lines · 125 tokens per session scan A 8c6595689c1f
migrating-dagster-to-airflow is a skill published in the GitHub repository astronomer/agents (439 stars, last pushed 5d ago), licensed Apache-2.0. It adds 125 tokens to every session and 3,401 once invoked, about $0.0006 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
workers-best-practices
Cloudflare Workers best practices for production applications. Use when writing, reviewing, or configuring Workers.
notion_synthesize
Synthesize durable ktx wiki pages and semantic-layer sources from staged Notion pages, databases, data-source rows, and clustered Notion evidence. Load when a WorkUnit contains Notion raw files or Notion evidence chunks.
historic_sql_table_digest
Convert one changed historic-SQL table usage bucket into typed table usage evidence for deterministic schema projection.
find-journalists
Build, refine, dedupe, and enrich small fit-checked journalist lists for newsjack campaigns. Uses the newsjack CLI (preferred) or the medialyst MCP for news search and journalist enrichment, and falls back to a best-effort local mode with no verified contacts; the agent owns how returned data is organized.
story-origin-check
Recover the first public timestamp and canonical major coverage for a newsjacking signal, then decide whether newer coverage is the same story, a different story, or a materially new development.
relevance-coarse-filter
Cheap, high-recall first-pass filter that removes obvious junk from a detector candidate pool before expensive story-origin research and PR judgment. Decides keep, monitoronly, or reject — never ranks, writes angles, verifies dates, or decides whether to pitch.