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/dryvist/claude-code-plugins/orchestrate-infranpx skills add dryvist/claude-code-plugins --skill orchestrate-infragit clone --depth 1 https://github.com/dryvist/claude-code-pluginsWrote 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/dryvist/claude-code-plugins/orchestrate-infra)<a href="https://agentmods.dev/skills/dryvist/claude-code-plugins/orchestrate-infra"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/orchestrate-infra.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.1 | $0.00018 | $0.00558 |
| Opus 5 | $0.00009 | $0.00279 |
| Sonnet 5 | $0.00004 | $0.00112 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
orchestrate-infra 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infrastructure Orchestrator
Master orchestrator for cross-repo infrastructure operations. Manages the dependency graph between Terraform and Ansible repositories and dispatches Task subagents for each phase.
Dependency Graph
tofu-proxmox
-> ansible-proxmox (host configuration)
-> ansible-proxmox-apps (application configuration)
-> ansible-splunk (Splunk Enterprise)
OpenTofu provisions infrastructure first through Terrakube. Ansible configures it in dependency order.
Supported Operations
plan-all
Run tofu plan in the tofu-proxmox Terrakube workspace, then
ansible-playbook --check across all Ansible repos in dependency order.
validate-all
Run tofu validate in tofu-proxmox, then ansible-playbook --syntax-check
across all Ansible repos.
sync-inventory
Export Terraform outputs as Ansible inventory and distribute to all Ansible repos. See /infra-sync-inventory for details.
e2e-test
Full pipeline validation: validate, plan, export inventory, syntax-check, check, diff. See /infra-e2e-test for details.
Execution Pattern
- Resolve repo paths: locate each target repo locally
- Dispatch OpenTofu phase: Launch a subagent for tofu-proxmox operations
- Await completion: OpenTofu must complete before Ansible phases
- Dispatch Ansible phases: Launch parallel subagents for independent Ansible repos (invoke
superpowers:dispatching-parallel-agents) - Collect results: Aggregate success/failure from all subagents
- Report: Summary with per-repo status
Secret Injection
Terrakube obtains short-lived OpenBao credentials through its native dynamic provider credential flow. Ansible uses native OpenBao lookups under its own policy. Never export, copy, or hardcode runtime credentials.
Error Handling
If any phase fails, report the failure and stop dependent phases. Independent repos continue in parallel.
Related Skills
- sync-inventory (infra-orchestration) — Export Terraform inventory and distribute to Ansible repositories
- test-e2e (infra-orchestration) — End-to-end infrastructure pipeline validation across Terraform and Ansible repos
- infrastructure-standards (infra-standards) — Use when working on infrastructure repos (terraform, ansible, kubernetes, proxmox, nix devShells)
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 · 66 lines · 18 tokens per session scan A 2c55f05f311a
orchestrate-infra is a skill published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 18 tokens to every session and 558 once invoked, about $0.0001 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-04.
Other skills, from other repositories
vast-gpu
Rent, manage, and destroy GPU instances on vast.ai. Use when user says "rent gpu", "vast.ai", "rent a server", "cloud gpu", or needs on-demand GPU without owning hardware.
pinme-r2
Use when a PinMe Cloudflare Worker needs R2 object storage, including secure file or image upload, streaming download, metadata lookup, deletion, listing, Range requests, or R2+D1 coordination. Guides AI to use PinMe's automatically injected env.R2 binding without R2 credentials or manual Wrangler configuration.
api-workers
Cloudflare Workers deployment using createWorkerHandler from @cyanheads/mcp-ts-core/worker. Covers the full handler signature, binding types, CloudflareBindings extensibility, runtime compatibility guards, and wrangler.toml requirements.
devops-cloud
DevOps, cloud infrastructure, and platform engineering. Use when working with AWS, GCP, Azure, Kubernetes, Terraform, CI/CD pipelines, or infrastructure as code.
cloudflare-workers-publish
Deploy static HTML files to Cloudflare Workers with 1Password credential management.
api-gateway
API Gateway patterns (Kong, Traefik, AWS API Gateway) — rate limiting, auth, routing, versioning. Use when implementing API gateway, reverse proxy, or API management.