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 FortiumPartners/ensemblenpx agentmods add plugins/fortiumpartners/ensemble/infrastructuregit clone --depth 1 https://github.com/FortiumPartners/ensembleWrote 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/fortiumpartners/ensemble/infrastructure)<a href="https://agentmods.dev/plugins/fortiumpartners/ensemble/infrastructure"><img src="https://agentmods.dev/badge/plugins/fortiumpartners/ensemble/infrastructure.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
ensemble-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.
What it actually says
{
"name": "ensemble-infrastructure",
"version": "5.3.0",
"description": "Infrastructure management for AWS, Kubernetes, Docker, Helm, Fly.io",
"author": {
"name": "Fortium Partners",
"email": "[email protected]",
"url": "https://github.com/FortiumPartners"
},
"repository": "https://github.com/FortiumPartners/ensemble",
"license": "MIT",
"keywords": [
"infrastructure",
"devops",
"kubernetes",
"aws",
"ensemble"
],
"commands": "./commands",
"skills": "./skills",
"agents": [
"./agents/build-orchestrator.md",
"./agents/deployment-orchestrator.md",
"./agents/helm-chart-specialist.md",
"./agents/infrastructure-developer.md",
"./agents/infrastructure-orchestrator.md",
"./agents/postgresql-specialist.md"
]
}
What it installs
The manifest is a name and a version. 11 skills, 7 agents travel with it, and installing the plugin installs all of them — 423 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill flyio A 0 tokens
- Skill helm A 0 tokens
- Skill kubernetes A 0 tokens
- Skill aws-cloud A 0 tokens
- Skill managing-supabase A 40 tokens
- Skill managing-linear-issues A 46 tokens
- Skill managing-railway A 35 tokens
- Skill managing-vercel A 38 tokens
- Skill cloud-provider-detector A 0 tokens
- Skill managing-jira-issues A 41 tokens
- Skill tooling-detector C 0 tokens
- Agent infrastructure-developer A 30 tokens
- Agent helm-chart-specialist A 35 tokens
- Agent infrastructure-specialist A 43 tokens
- Agent build-orchestrator A 28 tokens
- Agent deployment-orchestrator A 29 tokens
- Agent infrastructure-orchestrator A 26 tokens
- Agent postgresql-specialist A 32 tokens
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 · 30 lines scan A 25bb0f3ea68c
ensemble-infrastructure is a plugin published in the GitHub repository FortiumPartners/ensemble (11 stars, last pushed 1mo 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
daytona
Creates and manages isolated cloud sandboxes (secure code execution environments with dedicated runtimes) on the Daytona platform.
open-forge
Self-host open-source apps on your own cloud, your own VPS, your own Kubernetes cluster, a PaaS, or your own laptop. Chat-friendly interface to existing tools (aws, az, hcloud, doctl, gcloud, flyctl, kubectl, helm, podman, docker, lume, tailscale, terraform, cdk, ssh, gh) — Claude runs every command; you only answer…
agentic-workflows
Intelligent multi-agent swarms for automation - Ansible collections, Kubernetes operators, Terraform modules.
datum-platform
Kubernetes platform engineering automation with aggregated API servers, controller patterns, GitOps deployment, and platform capabilities.
technologies
Domain knowledge for infrastructure technologies - Terraform, OpenTofu, Packer, Ansible, Docker, Proxmox.
kubernetes-operations
Kubernetes manifest generation, networking configuration, security policies, observability setup, GitOps workflows, and auto-scaling.