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.
/plugin marketplace add EngineerWithAI/engineerwith-agentsnpx agentmods add plugins/engineerwithai/engineerwith-agents/cloud-infrastructuregit clone --depth 1 https://github.com/EngineerWithAI/engineerwith-agentsWrote 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/plugins/engineerwithai/engineerwith-agents/cloud-infrastructure)<a href="https://agentmods.dev/plugins/engineerwithai/engineerwith-agents/cloud-infrastructure"><img src="https://agentmods.dev/badge/plugins/engineerwithai/engineerwith-agents/cloud-infrastructure.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
cloud-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 2d 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.
What it actually says
{
"name": "cloud-infrastructure",
"source": "./plugins/cloud-infrastructure",
"description": "Cloud architecture design for AWS/Azure/GCP, Kubernetes cluster configuration, Terraform infrastructure-as-code, hybrid cloud networking, and multi-cloud cost optimization",
"version": "1.2.1",
"author": {
"name": "Mike Mayer",
"url": "https://github.com/EngineerWithAI"
},
"homepage": "https://github.com/EngineerWithAI/engineerwith-agents",
"repository": "https://github.com/EngineerWithAI/engineerwith-agents",
"license": "MIT",
"keywords": [
"cloud",
"aws",
"azure",
"gcp",
"kubernetes",
"terraform",
"infrastructure"
],
"category": "infrastructure",
"strict": false,
"commands": [],
"agents": [
"./agents/cloud-architect.md",
"./agents/kubernetes-architect.md",
"./agents/hybrid-cloud-architect.md",
"./agents/terraform-specialist.md",
"./agents/network-engineer.md",
"./agents/deployment-engineer.md",
"./agents/service-mesh-expert.md"
],
"skills": [
"./skills/cost-optimization",
"./skills/hybrid-cloud-networking",
"./skills/multi-cloud-architecture",
"./skills/terraform-module-library",
"./skills/istio-traffic-management",
"./skills/linkerd-patterns",
"./skills/mtls-configuration",
"./skills/service-mesh-observability"
]
}What it installs
The manifest is a name and a version. 8 skills travel with it, and installing the plugin installs all of them — 339 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill service-mesh-observability A 43 tokens
- Skill mtls-configuration A 38 tokens
- Skill istio-traffic-management A 40 tokens
- Skill hybrid-cloud-networking A 47 tokens
- Skill terraform-module-library A 42 tokens
- Skill cost-optimization A 38 tokens
- Skill multi-cloud-architecture A 50 tokens
- Skill linkerd-patterns B 41 tokens
What ships with it
1 file beside marketplace.json#cloud-infrastructure 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.
- 2d ago First seen · 44 lines scan A 7d0df9b7a8ce
cloud-infrastructure is a plugin published in the GitHub repository EngineerWithAI/engineerwith-agents (4 stars, last pushed 7mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-03.
Other plugins, from other repositories
elastic-observability
Elastic Observability skills - OpenTelemetry instrumentation and migration (.NET, Java, Python), LLM observability, log search, SLOs, and service health.
defang
Deploy Docker Compose apps to your own cloud account using Defang. Includes a /defang:deploy skill and Defang MCP server integration.
tailscale
Tailscale CLI reference and safe patterns for exposing local services over a tailnet.
cybrix-deploy
Deploy the current static site to a live HTTPS URL via Cybrix. Detects Next.js export, Astro, Vite, Hugo, Eleventy, and plain HTML. Returns a live URL on .cbrx.cc in under 60 seconds.
spacelift
Procedural guide and references for working with Spacelift via the spacelift-local MCP - manage stacks, runs, policies, spaces, integrations, and the lifecycle of cloud resources through Intent (OpenTofu/Terraform).
axcient
Every x360Recover endpoint, plus the fleet-wide backup-health answers the API alone can't give — offline, joined, and agent-ready.