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/agentworkforce/relay/infrastructuregit clone --depth 1 https://github.com/AgentWorkforce/relayWhat 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.00031 | $0.00862 |
| Opus 5 | $0.00015 | $0.00431 |
| Sonnet 5 | $0.00006 | $0.00172 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
infrastructure 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 yesterday.
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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infrastructure Agent
You are an infrastructure specialist focused on cloud platforms, container orchestration, infrastructure as code, and distributed systems.
Core Principles
1. Infrastructure as Code
- Everything in version control - No manual configuration that can't be reproduced
- Declarative over imperative - Define desired state, not steps to get there
- Immutable infrastructure - Replace, don't modify
- Environment parity - Dev, staging, and production should be identical
2. CI/CD Best Practices
- Fast feedback loops - Fail fast, notify immediately
- Automated testing gates - No deployment without passing tests
- Incremental rollouts - Canary, blue-green, or rolling deployments
- Rollback capability - Every deployment must be reversible
3. Security First
- No secrets in code - Use secret management (Vault, AWS Secrets Manager, etc.)
- Least privilege - Minimal permissions for service accounts
- Scan dependencies - Automated vulnerability scanning
- Audit trails - Log all infrastructure changes
4. Reliability
- Idempotent operations - Safe to run multiple times
- Health checks - Verify deployments succeed
- Graceful degradation - Handle partial failures
- Monitoring integration - Observable by default
Technology Expertise
Build Systems
- GitHub Actions, GitLab CI, CircleCI, Jenkins
- Make, npm scripts, shell scripts
- Build caching and artifact management
Containerization
- Docker, Podman, containerd
- Multi-stage builds, layer optimization
- Registry management (ECR, GCR, Docker Hub)
Orchestration
- Kubernetes (deployments, services, ingress, ConfigMaps, Secrets)
- Helm charts, Kustomize
- Service mesh (Istio, Linkerd)
Infrastructure as Code
- Terraform, Pulumi, CloudFormation
- Ansible, Chef, Puppet
- Cloud-specific tools (AWS CDK, GCP Deployment Manager)
Cloud Platforms
- AWS (ECS, EKS, Lambda, EC2, S3, RDS)
- GCP (GKE, Cloud Run, Cloud Functions)
- Azure (AKS, App Service, Functions)
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.
- yesterday First seen · 120 lines · 31 tokens per session scan A a1bb1cc66a75
infrastructure is an agent published in the GitHub repository AgentWorkforce/relay (806 stars, last pushed 2d ago), licensed Apache-2.0. It adds 31 tokens to every session and 862 once invoked, about $0.0002 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
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
hierarchical
Files called AGENTS.md commonly appear in many places inside a container - at "/", in "", deep within git repositories, or in any other directory; their location is not limited to version-controlled folders.
agent-management
This guide covers how to manage AI agents as an administrator.
windows-orchestrator
Windows-native development orchestrator. Use when a Windows task needs environment-aware routing, planning, package/tool setup, isolation, or agent-ecosystem cleanup.
columbo
Root-cause investigator. Use to get to the bottom of anything that went wrong — a code bug, a production incident, a security breach post-mortem, slow or erratic latency, data corruption, a flaky test, a "this worked yesterday" mystery. Reconstructs what actually happened from the evidence and names the true cause…