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/josstei/maestro-orchestrateWrote 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/agents/josstei/maestro-orchestrate/devops_engineer)<a href="https://agentmods.dev/agents/josstei/maestro-orchestrate/devops_engineer"><img src="https://agentmods.dev/badge/agents/josstei/maestro-orchestrate/devops_engineer/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/agents/josstei/maestro-orchestrate/devops_engineer"><img src="https://agentmods.dev/badge/agents/josstei/maestro-orchestrate/devops_engineer.svg" alt="Reviewed on agentmods" width="80" 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.00063 | $0.00192 |
| Opus 5.5 | $0.00025 | $0.00077 |
| Sonnet 5.5 | $0.00013 | $0.00038 |
| Haiku 4.5 | $0.00006 | $0.00019 |
Grade A, and why
devops_engineer 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
Agent methodology loaded via MCP tool get_agent. Call get_agent(agents: ["devops-engineer"]) to read the full methodology at delegation time.
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 · 24 lines · 63 tokens per session scan A 2389f367db68
devops_engineer is an agent published in the GitHub repository josstei/maestro-orchestrate (484 stars, last pushed 6d ago), licensed Apache-2.0. It adds 63 tokens to every session and 192 once invoked, about $0.0003 per session on Opus 5.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 agents, from other repositories
devops-engineer
DevOps specialist for the Hydraia pipeline. Authors CI/CD workflows, Dockerfiles/compose, and IaC following the repo's existing platform. Deploy steps, secrets, and destructive infra are written as human-approval plan tasks — never executed by the agent. Opt-in via /hydraia:devops.
ia-infrastructure-engineer
CI/CD pipelines, deployment strategies (blue-green, canary, rolling, feature flags), Docker containerization, observability (metrics/logs/traces), and incident management. Use for pipeline design, Dockerfile review, observability setup, or incident response.
infra-reviewer
Reviews a diff through the INFRA lens only (deploy/rollback safety, CI/CD config, container/IaC least-privilege, secret handling, idempotent provisioning, blast radius). Read-only. Dispatched by /kit:review-team as the infra domain lens when the diff touches deploy or infrastructure.
deploy-reviewer
Use this agent to review a repository's deployment setup read-only. Use when a Dockerfile, pipeline, health probe or Coolify configuration needs a second pair of eyes before it ships.
devops-engineer
Infrastructure & CI/CD expert for Docker, Kubernetes, GitHub Actions, and deployment automation.
pe-aws-infra
Principal AWS infrastructure engineer (AWS CDK/Cloudflare CDKTF/Terraform/GitHub Actions/Docker) reviewing infrastructure-as-code changes via five-pass protocol — Architecture → Quality+Tests → Security → Adversarial Re-read → Self-Adversarial. Reads full files, cross-verifies IAM grants against handler source code.…