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 diegosouzapw/awesome-omni-skills --skill airflow-dag-patterns-v2git clone --depth 1 https://github.com/diegosouzapw/awesome-omni-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/diegosouzapw/awesome-omni-skills/airflow-dag-patterns-v2)<a href="https://agentmods.dev/skills/diegosouzapw/awesome-omni-skills/airflow-dag-patterns-v2"><img src="https://agentmods.dev/badge/skills/diegosouzapw/awesome-omni-skills/airflow-dag-patterns-v2/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/diegosouzapw/awesome-omni-skills/airflow-dag-patterns-v2"><img src="https://agentmods.dev/badge/skills/diegosouzapw/awesome-omni-skills/airflow-dag-patterns-v2.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 76 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00079 | $0.02006 |
| Opus 5 | $0.00039 | $0.01003 |
| Sonnet 5 | $0.00016 | $0.00401 |
| Haiku 4.5 | $0.00008 | $0.00201 |
Grade A, and why
airflow-dag-patterns-v2 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.
Copies of this mod
4 near-identical copies found in the catalogue:
- airflow-dag-patterns — 97% identical, 18 lines differ
- airflow-dag-patterns-v3 — 91% identical, 28 lines differ
- anti-reversing-techniques-v2 — 86% identical, 62 lines differ
- anti-reversing-techniques — 84% identical, 64 lines differ
How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apache Airflow DAG Patterns
Overview
This public intake copy packages plugins/antigravity-awesome-skills/skills/airflow-dag-patterns from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.
Apache Airflow DAG Patterns Production-ready patterns for Apache Airflow including DAG design, operators, sensors, testing, and deployment strategies.
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Safety, Limitations.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
- Creating data pipeline orchestration with Airflow
- Designing DAG structures and dependencies
- Implementing custom operators and sensors
- Testing Airflow DAGs locally
- Setting up Airflow in production
- Debugging failed DAG runs
Operating Table
| Situation | Start here | Why it matters |
|---|---|---|
| First-time use | metadata.json |
Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow |
| Provenance review | ORIGIN.md |
Gives reviewers a plain-language audit trail for the imported source |
| Workflow execution | resources/implementation-playbook.md |
Starts with the smallest copied file that materially changes execution |
| Supporting context | resources/implementation-playbook.md |
Adds the next most relevant copied source file without loading the entire package |
| Handoff decision | ## Related Skills |
Helps the operator switch to a stronger native skill when the task drifts |
What ships with it
3 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.
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 First seen · 179 lines · 79 tokens per session scan A 29f47125263f
airflow-dag-patterns-v2 is a skill published in the GitHub repository diegosouzapw/awesome-omni-skills (140 stars, last pushed 2mo ago), licensed MIT. It adds 79 tokens to every session and 2,006 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
airflow
Build and troubleshoot Apache Airflow DAGs, operators, sensors, schedules, and retry behavior for data pipelines.
azure-cosmos-db
Expert knowledge for Azure Cosmos DB development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when using Cosmos DB SQL/Mongo/Cassandra APIs, change feed, vector search…
azure-local
Expert knowledge for Azure Local development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when planning Azure Local racks/SDN, disconnected clusters, Arc VMs, GPU workloads, or…
azure-arc
Expert knowledge for Azure Arc development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when managing Arc-enabled Kubernetes, data services, Edge Volumes, Agentic Retrieval APIs…
azure-defender-for-cloud
Expert knowledge for Azure Defender For Cloud development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when securing VMs, containers/AKS, SQL, storage, multi‑cloud connectors, or…
azure-functions
Expert knowledge for Azure Functions development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when wiring Functions to triggers/bindings, Cosmos/SQL/Service Bus, VNet/private…