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 agentmods add skills/apache/airflow/airflow-java-sdknpx skills add apache/airflow --skill airflow-java-sdkgit clone --depth 1 https://github.com/apache/airflowWhat 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 | $0.00119 | $0.01495 |
| Opus 5 | $0.00060 | $0.00747 |
| Sonnet 5 | $0.00024 | $0.00299 |
| Haiku 4.5 | $0.00012 | $0.00150 |
Grade A, and why
airflow-java-sdk 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 yesterday.
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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Airflow Java SDK contributor guide
The Java SDK lets Airflow tasks execute JVM code (Java, Kotlin, or any JVM language). You are helping a contributor work in one or both of these locations:
java-sdk/— the JVM-side library (Kotlin source, published to Maven)task-sdk/src/airflow/sdk/coordinators/java/— the Python coordinator that launches the JVM subprocess
Read these two documents early in every session — they contain the authoritative reference material:
airflow-core/docs/authoring-and-scheduling/language-sdks/java.rst— user-facing guide: annotation vs. interface API, XCom type mapping, Gradle/Maven steps, coordinator config.java-sdk/README.md— contributor guide: repository layout, detailed execution walkthrough, Gradle + Breeze test commands, coding conventions, common tasks, and PR checklist.
SDK package architecture
The JVM-side library is split into two packages with distinct visibility rules:
org.apache.airflow.sdk— public, user-facing API. Classes here (e.g.Client,Bundle,BundleBuilder,Server) are stable contracts that DAG authors and task implementers import directly. Changes to this package are breaking changes.org.apache.airflow.sdk.execution— internal implementation detail. Everything in this package (CoordinatorComm,LogSender,Log,Clientinexecution/, generated schema models, etc.) is not intended to be imported by users. It may change between releases without notice.
When reviewing or writing code, enforce this boundary: user task code and BundleBuilder
subclasses must only import from org.apache.airflow.sdk; any import of
org.apache.airflow.sdk.execution.* in user-facing API surface is a red flag.
Bundle composition and coordinator discovery
A bundle is a directory of JAR files (typically build/bundle/) placed on the coordinator's
jars_root. The coordinator scans the directory at task-dispatch time to find:
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.
- yesterday First seen · 135 lines · 119 tokens per session scan A 8905c19e0945
airflow-java-sdk is a skill published in the GitHub repository apache/airflow (46,647 stars, last pushed yesterday), licensed Apache-2.0. It adds 119 tokens to every session and 1,495 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
airflow-workflow
Execution guide for Airflow scheduled jobs — troubleshooting, updating, connid conventions, and cron references.
dagster-docs
Expert guidance for writing documentation for the Dagster docs website. ALWAYS use before creating or updating documentation in the docs directory.
git-workflow
Git operations: commits, branches, PRs, and conflict resolution.
jamjet-durability-patterns
Production durability patterns for AI agents on the JVM — crash recovery, audit trails, human-in-the-loop, and replay testing using JamJet runtime.
bugsweep
Systematic bug sweep with a codebase-scaled target value, doubling escalation, area tracking, and final verification. Use on /bugsweep or whenever the user requests a systematic bug pass.
compare-race
Use when the user wants to send the same prompt to several LLMs and compare the answers - sequentially (stopwatch, clean per-lane timing) or in parallel (true race), with optional repetitions per model, judged by the starting model across quality, correctness, completeness, instruction fidelity and latency (time is…