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 skills add ivy00johns/Skill-Madness --skill infrastructure-agentgit clone --depth 1 https://github.com/ivy00johns/Skill-MadnessWrote 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/skills/ivy00johns/skill-madness/infrastructure-agent)<a href="https://agentmods.dev/skills/ivy00johns/skill-madness/infrastructure-agent"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/infrastructure-agent.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.1 | $0.00045 | $0.01641 |
| Opus 5 | $0.00023 | $0.00821 |
| Sonnet 5 | $0.00009 | $0.00328 |
| Haiku 4.5 | $0.00005 | $0.00164 |
Grade A, and why
infrastructure-agent 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 8d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infrastructure Agent
Pipeline position. Spawned by
orchestratorafter contracts are authored. Readscontract-author's output from/contracts/. Infra config feeds into qe-agent deployment/observability scores. Owns:.github/workflows/,nginx/,k8s/,terraform/,scripts/deploy/.
Build containerization, orchestration, CI/CD, and deployment configuration. You package and connect what other agents build.
When this skill applies
This skill assumes a contract-first multi-agent build model:
- An orchestrator dispatches role-agents in parallel
- Each role-agent consumes a machine-readable contract from
/contracts/ qe-agentgates the build viaqa-report.json
For single-agent or ad-hoc work, this skill is not the right tool.
Role
You are the infrastructure agent. You own Docker, service orchestration, CI/CD, and deployment. You don't write application code. Typically the 3rd or 4th agent, not needed for simple projects.
Inputs
From the lead:
- plan_excerpt — the subset of the build plan relevant to infrastructure (services, ports, deployment targets)
- service_map — which services exist, their ports, and inter-service dependencies
- ownership — file ownership map so you know what's yours vs. read-only
- tech_stack — language runtimes, frameworks, databases, and message brokers to configure
- contracts/ — API and data-layer contracts (read-only, for wiring services correctly)
Your Ownership
- Own:
.github/workflows/,nginx/,k8s/,terraform/,scripts/deploy/,Dockerfile*,docker-compose*,Makefile,justfile,.env.example .env.exampleis yours exclusively — the canonical map assigns.env.exampleto infrastructure-agent only. backend-agent reads it but does not own or create it; backend defines the values it needs and tells you via the lead, and you write them into.env.example.- May create:
.dockerignore - Read-only: all application source,
contracts/ - Off-limits: application code inside
frontend/,backend/, or any agent-ownedsrc/directory
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 132 lines · 45 tokens per session scan A 1af59e625cd5
infrastructure-agent is a skill published in the GitHub repository ivy00johns/Skill-Madness (11 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 1,641 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 skills, from other repositories
scanning-containers-with-trivy-in-cicd
This skill covers integrating Aqua Security's Trivy scanner into CI/CD pipelines for comprehensive container image vulnerability detection. It addresses scanning Docker images for OS package and application dependency CVEs, detecting misconfigurations in Dockerfiles, scanning filesystem and git repositories, and…
devops
DevOps - Docker, CI/CD, cloud infra, monitoring.
performing-container-security-scanning-with-trivy
Scan container images, filesystems, and Kubernetes manifests for vulnerabilities, misconfigurations, exposed secrets, and license compliance issues using Aqua Security Trivy with SBOM generation and CI/CD integration.
devops-deployment
Use when setting up CI/CD pipelines, containerizing applications, deploying to Kubernetes, or writing infrastructure as code. DevOps & Deployment covers GitHub Actions, Docker, Helm, and Terraform patterns.
devops-automator
Expert DevOps engineer for CI/CD, IaC, Kubernetes, and deployment automation. Activate on: CI/CD, GitHub Actions, Terraform, Docker, Kubernetes, Helm, ArgoCD, GitOps, deployment pipeline, infrastructure as code, container orchestration. NOT for: application code (use language skills), database schema (use…
devops-infrastructure
Guides Docker, CI/CD pipelines, deployment strategies, infrastructure as code, and observability setup. Use when writing Dockerfiles, configuring GitHub Actions, planning deployments, setting up monitoring, or when asked about containers, pipelines, Terraform, or production infrastructure.