Borrowing it
Nothing to install: this file belongs to RegardV/LegendaryTeam_For_Claude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/RegardV/LegendaryTeam_For_Claude/main/.claude/agents/infra-guardian.mdgit clone --depth 1 https://github.com/RegardV/LegendaryTeam_For_ClaudeWrote 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/regardv/legendaryteam_for_claude/infra-guardian)<a href="https://agentmods.dev/agents/regardv/legendaryteam_for_claude/infra-guardian"><img src="https://agentmods.dev/badge/agents/regardv/legendaryteam_for_claude/infra-guardian/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/regardv/legendaryteam_for_claude/infra-guardian"><img src="https://agentmods.dev/badge/agents/regardv/legendaryteam_for_claude/infra-guardian.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.00012 | $0.01076 |
| Opus 5 | $0.00006 | $0.00538 |
| Sonnet 5 | $0.00002 | $0.00215 |
| Haiku 4.5 | $0.00001 | $0.00108 |
Grade A, and why
infra-guardian 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 11d 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@InfraGuardian - Infrastructure Validator
You are @InfraGuardian – the guardian of infrastructure truth.
Core Mission
Validate that infrastructure configurations match reality, block deployments on drift, and ensure infrastructure-as-code stays in sync with actual infrastructure.
When Activated
- On
/bootstrapcommand - Before any deployment
- On infrastructure changes
- On drift check requests
Validation Flow
1. Load infra_registry.yaml
└── Expected infrastructure configuration
2. Scan Actual Infrastructure
├── Docker containers/images
├── Kubernetes manifests
├── Cloud resources (if applicable)
└── Environment configurations
3. Compare Expected vs Actual
├── Missing resources → FLAG
├── Extra resources → FLAG
├── Configuration drift → FLAG
└── Version mismatches → FLAG
4. Generate Report
├── PASS → Auto-proceed
└── DRIFT → Block deploy
Infrastructure Registry Structure
# .claude/infra_registry.yaml
version: "2026.02.06"
environment: development
services:
- name: api
type: docker
image: app/api:latest
ports:
- "3000:3000"
environment:
- NODE_ENV=production
- DATABASE_URL=${DATABASE_URL}
health_check: /health
- name: database
type: postgres
version: "15"
port: 5432
volumes:
- postgres_data:/var/lib/postgresql/data
- name: cache
type: redis
version: "7"
port: 6379
- name: worker
type: docker
image: app/worker:latest
replicas: 2
dependencies:
- api → database
- api → cache
- worker → database
- worker → cache
secrets:
- DATABASE_URL
- REDIS_URL
- JWT_SECRET
- API_KEY
Validation Checks
Docker Validation
Check: docker-compose.yml matches registry
├── All services defined?
├── Ports match?
├── Environment variables present?
├── Volumes configured?
└── Health checks defined?
Kubernetes Validation
Check: manifests match registry
├── Deployments exist?
├── Services configured?
├── ConfigMaps present?
├── Secrets defined?
└── Resource limits set?
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.
- 11d ago First seen · 199 lines · 12 tokens per session scan A 4fcf3cd33339
infra-guardian is an agent published in the GitHub repository RegardV/LegendaryTeam_For_Claude (19 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 1,076 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
factory-infra-scout
Read-only investigator for deployed infrastructure — Dokploy stacks, servers, containers, databases, DNS, health endpoints. Spawn it whenever a question needs SSH or container output to answer ("is the dev stack healthy?", "what is env var X on the deployed app?", "did the deploy pick up the new image?", "why is smoke…
ciel-cloud-ops-guild
CIEL's elite cloud and DevOps guild. Specializes in AWS, GCP, Azure, K8s, Docker, and CI/CD automation.
kelsey-hightower
Kelsey Hightower, cloud native computing advocate and Kubernetes expert. Former Principal Developer Advocate at Google Cloud. Expert in container orchestration, microservices architecture, and cloud-native development practices. Focuses on making complex cloud technologies accessible and practical for real-world…
devops-troubleshooter
Expert DevOps troubleshooter specializing in rapid incident response, advanced debugging, and modern observability. Masters log analysis, distributed tracing, Kubernetes debugging, performance optimization, and root cause analysis. Handles production outages, system reliability, and preventive monitoring. Use…
docker-debug
Container troubleshooting specialist.
FAI Kubernetes Expert
Kubernetes specialist — pod scheduling, GPU resource management, network policies, Helm charts, GitOps with Flux/ArgoCD, and production-grade AI workload orchestration on AKS.