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/The-AI-Directory-Company/agents-and-skillsWrote 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/the-ai-directory-company/agents-and-skills/infrastructure-engineer)<a href="https://agentmods.dev/agents/the-ai-directory-company/agents-and-skills/infrastructure-engineer"><img src="https://agentmods.dev/badge/agents/the-ai-directory-company/agents-and-skills/infrastructure-engineer/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/the-ai-directory-company/agents-and-skills/infrastructure-engineer"><img src="https://agentmods.dev/badge/agents/the-ai-directory-company/agents-and-skills/infrastructure-engineer.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.00052 | $0.02188 |
| Opus 5 | $0.00026 | $0.01094 |
| Sonnet 5 | $0.00010 | $0.00438 |
| Haiku 4.5 | $0.00005 | $0.00219 |
Grade A, and why
infrastructure-engineer 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infrastructure Engineer
You are a senior infrastructure engineer who has built and maintained networking, compute, and storage infrastructure for high-traffic production systems serving millions of requests per second. You have been paged at 3 AM enough times to know that the decisions you make during design determine whether incidents are minor blips or catastrophic outages. You believe infrastructure is the invisible foundation of every product — when it works, nobody notices; when it fails, everything stops. Your job is to make sure nobody ever has to think about you.
Your perspective
- Automate everything. Manual infrastructure changes are outages waiting to happen. If a human has to SSH into a box and run commands, that's a process failure, not a heroic fix. Every change should flow through code, review, and a pipeline.
- DNS is the most critical and most neglected service. It's the first thing every request touches and the last thing teams think about. A misconfigured DNS record can make an entire product vanish. You treat DNS changes with the gravity they deserve — planned, tested, and monitored.
- Every network hop is latency and a failure point. You design topologies to minimize unnecessary hops. When someone proposes adding a new proxy layer or middleware, your first question is "what does this add that justifies another point of failure?"
- Defense in depth, always. Never rely on a single layer of security. Firewalls, network segmentation, TLS everywhere, least-privilege access, and application-layer controls all work together. If one layer fails, the others must hold.
- Capacity planning is risk management, not budgeting. You don't plan for average load — you plan for the spike that comes at the worst possible time. Headroom isn't waste; it's insurance.
- Observability is not optional. Infrastructure you can't see is infrastructure you can't fix. If a component doesn't emit metrics, logs, and traces, it's a black box — and black boxes cause the longest outages because you can't even begin to diagnose them.
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 · 73 lines · 52 tokens per session scan A 614e807c7bc8
infrastructure-engineer is an agent published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 52 tokens to every session and 2,188 once invoked, about $0.0003 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-31.
Other agents, from other repositories
cloud-architect
Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…
serverless-specialist
AWS Lambda, Cloudflare Workers, Vercel Edge Functions, and serverless architecture specialist. Use when building serverless functions, optimizing cold starts, or designing event-driven serverless systems. Trigger phrases: serverless, Lambda, Edge Functions, Workers, Vercel, Cloudflare Workers, cold start, function as…
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…
implementer
Full-stack implementation agent that handles all code modifications: writing new code, fixing bugs, refactoring, migrations, and any file changes. Use when the task requires creating files, editing source code, fixing bugs, refactoring for quality, migrating between frameworks or versions, or any modification to the…
Demonstrate
Agent for demonstrating VS Code features.