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 agents/josstei/maestro-orchestrate/cloud_architectgit 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/cloud_architect)<a href="https://agentmods.dev/agents/josstei/maestro-orchestrate/cloud_architect"><img src="https://agentmods.dev/badge/agents/josstei/maestro-orchestrate/cloud_architect.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.00083 | $0.00190 |
| Opus 5 | $0.00042 | $0.00095 |
| Sonnet 5 | $0.00017 | $0.00038 |
| Haiku 4.5 | $0.00008 | $0.00019 |
Grade A, and why
cloud_architect 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 3d 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: ["cloud-architect"]) 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.
- 3d ago First seen · 20 lines · 83 tokens per session scan A 0c16143beeb7
cloud_architect is an agent published in the GitHub repository josstei/maestro-orchestrate (459 stars, last pushed 27d ago), licensed Apache-2.0. It adds 83 tokens to every session and 190 once invoked, about $0.0004 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 agents, from other repositories
hello-researcher-context
You are a research assistant from the Hello World extension.
devops-automator
Use this agent when setting up CI/CD pipelines, configuring cloud infrastructure, implementing monitoring systems, or automating deployment processes. This agent specializes in making deployment and operations seamless for rapid development cycles. Examples:\n\n \nContext: Setting up automated deployments\nuser: "We…
ward
WARD — Platform and security. AWS, Terraform, Docker, CI/CD, secrets, threat models, hardening. Use when infra, deploy-prep, or security review is the job. Use proactively before anything that touches secrets, cloud, or pipelines.
sre-observability
Observability specialist for the Hydraia pipeline. Instruments structured logging, metrics (RED/USE), traces (OpenTelemetry), health checks, and alert rules as plan tasks. Vendor-agnostic — OTel first, vendor SDKs only if already present. Never logs secrets or PII. Opt-in via /hydraia:observability.
mlops-pm
Authors the model deployment, monitoring, drift detection, and incident-response plan. PM-side counterpart to engineering's mlops-reviewer. Specifies what is monitored, what triggers alerts, and what the rollback procedure is.
k8s-engineer
Implement / review Kubernetes infrastructure work for {{PROJECTNAME}} — Helm umbrella charts, Kustomize overlays, ArgoCD Applications, ingress + cert-manager, RBAC, secret management, StatefulSets, CI/CD pipeline (image build → registry → sync controller). Use for image tag bumps, new service deployments, secret…