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.
git 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/plugins/astronomer/agents/agents)<a href="https://agentmods.dev/plugins/astronomer/agents/agents"><img src="https://agentmods.dev/badge/plugins/astronomer/agents/agents/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/plugins/astronomer/agents/agents"><img src="https://agentmods.dev/badge/plugins/astronomer/agents/agents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
astronomer-data 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 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.
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.
What it actually says
{
"name": "astronomer-data",
"version": "0.1.0",
"description": "Data engineering plugin - warehouse exploration, pipeline authoring, Airflow integration",
"hooks": {
"SessionStart": [
{
"hooks": [
{
"type": "command",
"command": "${CLAUDE_PLUGIN_ROOT}/skills/airflow/hooks/warm-uvx-cache.sh",
"async": true
}
]
}
],
"Stop": [
{
"hooks": [
{
"type": "command",
"command": "uv run ${CLAUDE_PLUGIN_ROOT}/skills/analyzing-data/scripts/cli.py stop"
}
]
}
]
}
}
What it installs
The manifest is a name and a version. 35 skills, 3 commands travel with it, and installing the plugin installs all of them — 3,524 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill airflow-hitl A 126 tokens
- Skill blueprint A 66 tokens
- Skill airflow-plugins A 147 tokens
- Skill airflow-state-store A 243 tokens
- Skill airflow A 186 tokens
- Skill cosmos-dbt-core A 73 tokens
- Skill dag-factory A 80 tokens
- Skill delegating-to-otto A 208 tokens
- Skill migrating-ai-sdk-to-common-ai A 151 tokens
- Skill migrating-dagster-to-airflow A 125 tokens
- Skill annotating-task-lineage A 51 tokens
- Skill creating-openlineage-extractors A 51 tokens
- Skill deploying-airflow A 48 tokens
- Skill authoring-go-sdk-tasks A 165 tokens
- Skill authoring-java-sdk-tasks A 152 tokens
- Skill configuring-airflow-language-sdks A 155 tokens
- Skill migrating-airflow-2-to-3 A 98 tokens
- Skill testing-dags A 77 tokens
- Skill troubleshooting-astro-deployments A 40 tokens
- Skill warehouse-init A 54 tokens
- Skill authoring-dags A 93 tokens
- Skill authoring-language-sdk-tasks A 153 tokens
- Skill debugging-dags A 111 tokens
- Skill deploying-go-sdk-bundles A 146 tokens
- Skill managing-astro-deployments A 41 tokens
- Skill managing-astro-local-env A 63 tokens
- Skill analyzing-data A 78 tokens
- Skill tracing-downstream-lineage A 48 tokens
- Skill profiling-tables A 52 tokens
- Skill tracing-upstream-lineage A 40 tokens
- Skill checking-freshness A 44 tokens
- Skill setting-up-astro-project A 53 tokens
- Skill airflow-adapter A 46 tokens
- Skill deploying-java-sdk-bundles C 146 tokens
- Skill cosmos-dbt-fusion C 83 tokens
- Command add-adapter-method A 9 tokens
- Command add-tool A 8 tokens
- Command check-airflow-compat A 14 tokens
What ships with it
1 file beside plugin.json 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 First seen · 29 lines scan A d98c93999c4d
astronomer-data is a plugin published in the GitHub repository astronomer/agents (453 stars, last pushed 2d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
developer-kit-ai
AI/ML capabilities including prompt engineering, RAG, and chunking strategies.
capacitor-core
Core Capacitor skills for best practices, plugin selection, and MCP automation.
contentful
Agent skills for Contentful apps, APIs, migrations, and personalization.
powabase
Build on Powabase — the AI Backend-as-a-Service (RAG, agents, orchestration, workflows) plus a Supabase-style BaaS layer. Bundles the powabase agent skill under skills/.
machine-learning-ops
ML pipeline design, experiment tracking, model evaluation, training debugging, and reproducibility.
ls-agent
Agent behavior skills.