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/docxology/template/orchestrationnpx skills add docxology/template --skill orchestrationgit clone --depth 1 https://github.com/docxology/templateWrote 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/docxology/template/orchestration)<a href="https://agentmods.dev/skills/docxology/template/orchestration"><img src="https://agentmods.dev/badge/skills/docxology/template/orchestration.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00055 | $0.00157 |
| Opus 5 | $0.00028 | $0.00078 |
| Sonnet 5 | $0.00011 | $0.00031 |
| Haiku 4.5 | $0.00006 | $0.00016 |
Grade A, and why
infrastructure-orchestration 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 4d 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
Orchestration (Layer 1)
Entry: python -m infrastructure.orchestration (build_parser, main from cli.py).
Key imports
from infrastructure.orchestration import (
PipelineRunner,
validate_project_slug,
select_project_interactive,
setup_stage_log,
run_secure_pipeline,
)
Tests
uv run pytest tests/infra_tests/orchestration/ -v
What ships with it
14 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.
- __init__.py 1.8 KB runs code
- __main__.py 185 B runs code
- AGENTS.md 3.0 KB
- cli.py 2.6 KB runs code
- commands.py 5.4 KB runs code
- discovery.py 6.8 KB runs code
- interactive.py 3.6 KB runs code
- link_sync.py 3.2 KB runs code
- menu.py 9.7 KB runs code
- parser.py 5.5 KB runs code
- pipeline_runner.py 6.9 KB runs code
- README.md 1.1 KB
- secure_run.py 11 KB runs code
- stage_logger.py 3.2 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.
- 4d ago First seen · 27 lines · 55 tokens per session scan A 51d980774358
infrastructure-orchestration is a skill published in the GitHub repository docxology/template (19 stars, last pushed today), licensed Apache-2.0. It adds 55 tokens to every session and 157 once invoked, about $0.0003 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
planning-with-files
Persistent file-based planning for multi-step AI-agent work. Keeps taskplan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and…
aerospace-engineering-technician
Use when a task needs the judgment of an Aerospace Engineering and Operations Technologist/Technician — verifying an installed fastener's preload against a drawing's torque callout via the T=K·D·F relationship, reducing strain-gauge data from a structural proof-load test into stress and checking it against an…
actor
Use when a task needs the judgment of a professional Actor — breaking down sides for a self-tape audition, preparing a character choice for rehearsal, deciding between two conflicting bookings, reading a contract offer for scale vs. scale-plus terms, or diagnosing why callbacks aren't converting to bookings.
agricultural-equipment-operator
Use when a task needs the judgment of an Agricultural Equipment Operator — calibrating planter seed population and singulation, diagnosing combine header or separator loss, sequencing planting or harvest across fields under a weather-constrained window, sizing machinery capacity in acres/hour against a season's…
agricultural-inspector
Use when a task needs the judgment of an Agricultural Inspector — grading a lot of produce against a USDA grade standard's defect tolerances, evaluating agricultural water test results against FSMA microbial thresholds, checking a pesticide residue result against the commodity-specific EPA tolerance, deciding whether…
agricultural-manager
Use when a task needs the judgment of a Farmer, Rancher, or other Agricultural Manager — deciding a planting/breeding mix or acreage shift under price and weather uncertainty, sizing a hedge or crop-insurance coverage level, running break-even and diversification scenarios before a capital or input commitment, or…