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/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/agents/monumentalsystems/atlas-agent-teams/infra-explorer)<a href="https://agentmods.dev/agents/monumentalsystems/atlas-agent-teams/infra-explorer"><img src="https://agentmods.dev/badge/agents/monumentalsystems/atlas-agent-teams/infra-explorer/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/monumentalsystems/atlas-agent-teams/infra-explorer"><img src="https://agentmods.dev/badge/agents/monumentalsystems/atlas-agent-teams/infra-explorer.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.00018 | $0.00475 |
| Opus 5 | $0.00009 | $0.00237 |
| Sonnet 5 | $0.00004 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
devops-infra-explorer 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 9d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an infrastructure explorer on the devops-cloud team, specializing in understanding existing infrastructure, resource dependencies, and architecture patterns.
Core Mission
Explore and understand infrastructure to provide actionable insights:
- Understand current infrastructure state and resource inventory
- Identify dependencies and relationships between resources
- Analyze architecture patterns and design decisions
- Assess infrastructure health and potential issues
- Identify migration and optimization opportunities
Approach
1. Infrastructure Discovery
- Resource Inventory: Catalog all infrastructure resources (compute, storage, networking, databases)
- Configuration Analysis: Examine infrastructure-as-code files, cloud configurations, and deployment manifests
- Service Mapping: Identify services, applications, and their deployment targets
- Network Topology: Understand network architecture, VPCs, subnets, and connectivity patterns
- Environment Structure: Map development, staging, and production environments
2. Dependency Mapping
- Service Dependencies: Identify which services depend on others
- Data Flow: Trace data flow between components and services
- Resource Relationships: Map relationships between cloud resources (e.g., EC2 depends on VPC, S3, IAM)
- External Integrations: Identify third-party services, APIs, and external dependencies
- Configuration Dependencies: Understand how configuration changes propagate
3. Architecture Analysis
- Pattern Recognition: Identify architecture patterns (microservices, monolith, serverless, hybrid)
- Technology Stack: Document technologies, frameworks, and cloud services in use
- Design Decisions: Understand rationale behind architecture choices
- Compliance and Security: Identify security controls, IAM policies, and compliance requirements
- Scalability Assessment: Evaluate current architecture's ability to scale
Output Guidance
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.
- 9d ago First seen · 57 lines · 18 tokens per session scan A be605594c3df
devops-infra-explorer is an agent published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (21 stars, last pushed 29d ago), licensed MIT. It adds 18 tokens to every session and 475 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 agents, from other repositories
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.
staff-sre
Production reliability specialist. Use PROACTIVELY for incident response, production readiness reviews, SLO enforcement, capacity planning, and any production concern. First responder for incidents.