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 commands/astronomer/agents/add-toolgit clone --depth 1 https://github.com/astronomer/agentsWhat 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.00008 | $0.00243 |
| Opus 5 | $0.00004 | $0.00121 |
| Sonnet 5 | $0.00002 | $0.00049 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
add-tool 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 2d 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
1 near-identical copy found in the catalogue:
- add-tool — 100% identical, 0 lines differ
What it actually says
Add a new MCP tool named $ARGUMENTS to src/astro_airflow_mcp/server.py.
Steps
-
If the tool needs a new adapter method, run
/add-adapter-methodfirst. -
Create internal
_implfunction that calls the adapter:
def _tool_name_impl(param: str) -> str:
"""Internal implementation."""
try:
adapter = _get_adapter()
data = adapter.method_name(param)
return json.dumps(data, indent=2)
except Exception as e:
return str(e)
- Create the MCP tool with descriptive docstring:
@mcp.tool()
def tool_name(param: str) -> str:
"""One-line description.
Use this tool when the user asks about:
- "Example query 1"
- "Example query 2"
Args:
param: Description
Returns:
JSON with response data
"""
return _tool_name_impl(param=param)
- Add the tool to README.md tools table.
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.
- 2d ago First seen · 46 lines · 8 tokens per session scan A b92b02edc9a8
add-tool is a command published in the GitHub repository astronomer/agents (432 stars, last pushed 15d ago), licensed Apache-2.0. It adds 8 tokens to every session and 243 once invoked, about $0.0000 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 commands, from other repositories
build-agent
Build an AI agent on Cloudflare using the Agents SDK.
remoto-run
Orchestrate a task across remote headless agents on the Jetson (spawn, wait, collect, cross-review).
ship-an-mcp-server
Workflow recipe — make your product agent-usable by chaining 4 skills, spec to pricing.
auto
Intent-classified router, the front door to OrchestKit and the DEFAULT entry point for any goal-shaped request. Classifies a plain-English goal and routes it to the right specialist skill. Routing is never overhead, so use it even when the target skill seems obvious; skip only when already executing inside another…
loop-forge
Turn a one-line repetitive task into a reusable, self-guarding slash command (loop-forge).
git
Git operations with intelligent commit messages and workflow optimization.