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/sponticelli/gamedev-claude-pluginsWrote 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/sponticelli/gamedev-claude-plugins/devops)<a href="https://agentmods.dev/plugins/sponticelli/gamedev-claude-plugins/devops"><img src="https://agentmods.dev/badge/plugins/sponticelli/gamedev-claude-plugins/devops/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/plugins/sponticelli/gamedev-claude-plugins/devops"><img src="https://agentmods.dev/badge/plugins/sponticelli/gamedev-claude-plugins/devops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
devops 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 1mo 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": "devops",
"description": "CI/CD pipelines, automated testing, build systems, deployment, and infrastructure for game development",
"version": "1.0.0",
"author": {
"name": "GameDev Plugins"
},
"repository": "https://github.com/sponticelli/gamedev-claude-plugins",
"license": "MIT",
"agents": [
"./agents/pipeline-architect.md",
"./agents/build-engineer.md",
"./agents/test-automation-lead.md",
"./agents/infrastructure-planner.md",
"./agents/deployment-coordinator.md",
"./agents/verify-pipeline.md"
],
"commands": [
"./commands/pipeline-spec.md",
"./commands/build-audit.md",
"./commands/test-strategy.md",
"./commands/infra-plan.md",
"./commands/deploy-checklist.md",
"./commands/incident-response.md"
]
}
What it installs
The manifest is a name and a version. 6 commands, 6 agents travel with it, and installing the plugin installs all of them — 211 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Command incident-response A 8 tokens
- Command deploy-checklist A 10 tokens
- Command infra-plan A 7 tokens
- Command test-strategy A 10 tokens
- Command build-audit A 10 tokens
- Command pipeline-spec A 13 tokens
- Agent build-engineer A 26 tokens
- Agent deployment-coordinator A 23 tokens
- Agent infrastructure-planner A 27 tokens
- Agent test-automation-lead A 30 tokens
- Agent verify-pipeline A 22 tokens
- Agent pipeline-architect A 25 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.
- 1mo ago First seen · 27 lines scan A 7c4222348138
devops is a plugin published in the GitHub repository sponticelli/gamedev-claude-plugins (17 stars, last pushed 9mo 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-08-30.
Other plugins, from other repositories
asset-pipelines
Game asset pipelines: import settings, texture atlasing, LOD generation, audio compression, and CI asset validation for Godot and Unity.
cicd-automation
CI/CD pipeline configuration, GitHub Actions/GitLab CI workflow setup, and automated deployment pipeline orchestration.
godot
Develop, test, build, and deploy Godot 4.x games. Includes GdUnit4 testing, PlayGodot automation, web/desktop exports, CI/CD pipelines, and deployment.
asset-pipelines
Game asset pipelines: import settings, texture atlasing, LOD generation, audio compression, and CI asset validation for Godot and Unity.
jk
GitHub CLI-style interface for Jenkins controllers - create multibranch jobs, inspect config.xml, and manage runs, logs, artifacts, credentials, nodes, and queues.
bevy-skills
AI agent skills for Bevy 0.19: ECS, rendering, physics, input, assets, audio, accessibility, persistence, testing, profiling, voxels, and migration.