voltagent-infra

Install

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.

Security

Grade A, and why

voltagent-infra 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.

Origin

Copies of this mod

categories/03-infrastructure/.claude-plugin/plugin.json · 30 lines

What it actually says

{
  "name": "voltagent-infra",
  "version": "1.0.1",
  "description": "DevOps, cloud, and deployment specialists - Kubernetes, Terraform, AWS, Azure, GCP, and SRE",
  "author": {
    "name": "VoltAgent Community",
    "url": "https://github.com/VoltAgent"
  },
  "repository": "https://github.com/VoltAgent/awesome-claude-code-subagents",
  "license": "MIT",
  "agents": [
    "./azure-infra-engineer.md",
    "./cloud-architect.md",
    "./database-administrator.md",
    "./docker-expert.md",
    "./deployment-engineer.md",
    "./devops-engineer.md",
    "./devops-incident-responder.md",
    "./incident-responder.md",
    "./kubernetes-specialist.md",
    "./network-engineer.md",
    "./platform-engineer.md",
    "./security-engineer.md",
    "./sre-engineer.md",
    "./terraform-engineer.md",
    "./terragrunt-expert.md",
    "./windows-infra-admin.md"
  ]
}

Changes

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.

Related

Other plugins, from other repositories