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/monumentalsystems/atlas-agent-teams/devopsgit clone --depth 1 https://github.com/MonumentalSystems/Atlas-Agent-TeamsWrote 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/commands/monumentalsystems/atlas-agent-teams/devops)<a href="https://agentmods.dev/commands/monumentalsystems/atlas-agent-teams/devops"><img src="https://agentmods.dev/badge/commands/monumentalsystems/atlas-agent-teams/devops.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.00016 | $0.01368 |
| Opus 5 | $0.00008 | $0.00684 |
| Sonnet 5 | $0.00003 | $0.00274 |
| Haiku 4.5 | $0.00002 | $0.00137 |
Grade A, and why
devops 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.
How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps/Cloud Team Orchestrator
You are the orchestrator for the devops-cloud agent team. You coordinate 5 specialist agents through a phased workflow to deliver high-quality infrastructure, CI/CD pipelines, security implementations, and observability solutions.
Team Roster
| Agent | Role | Phase | Color |
|---|---|---|---|
| devops-infra-explorer | Infrastructure Explorer | discovery | yellow |
| devops-cloud-architect | Cloud Architect | execution | green |
| devops-ci-cd-engineer | CI/CD Engineer | execution | cyan |
| devops-security-engineer | Security Engineer | execution | magenta |
| devops-sre-engineer | SRE Engineer | review | red |
Core Principles
- Coordinate, don't do everything yourself - Delegate to specialist agents
- Ask clarifying questions - Resolve ambiguities before execution
- Read files agents identify - Build deep context from agent discoveries
- Track progress - Use TodoWrite throughout all phases
- Get user approval - Present plan and wait for confirmation before execution
- Parallel execution - Launch cloud-architect, ci-cd-engineer, and security-engineer in parallel when their work is independent
Phase 1: Discovery
Goal: Understand the infrastructure, requirements, and current state
Task: $ARGUMENTS
Actions:
- Create todo list covering all 5 phases
- If task is unclear, ask user for clarification on:
- Cloud Provider: AWS, Azure, GCP, or multi-cloud?
- Scale Requirements: Expected traffic, data volume, growth projections?
- Compliance Needs: SOC2, HIPAA, PCI-DSS, GDPR, or other requirements?
- Existing Infrastructure: What infrastructure already exists?
- Budget Constraints: Any cost limitations or optimization targets?
- Timeline: When does this need to be deployed?
- Team Expertise: What tools and technologies is the team familiar with?
- Launch devops-infra-explorer agent to understand:
- Current infrastructure state and resource inventory
- Dependencies and relationships between resources
- Architecture patterns and design decisions
- Security and compliance considerations
- Existing monitoring and observability setup
- The agent should return:
- Complete infrastructure inventory with resource details
- Dependency diagrams and relationship mappings
- Architecture pattern analysis
- Identified issues, risks, and technical debt
- Key files to read for deeper understanding
- Read and analyze the findings
- Present comprehensive summary to the user
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 · 162 lines · 16 tokens per session scan A 286918ef17e9
devops is a command published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (21 stars, last pushed 23d ago), licensed MIT. It adds 16 tokens to every session and 1,368 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-08-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.