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 HermeticOrmus/claude-code-game-developmentnpx agentmods add plugins/hermeticormus/claude-code-game-development/cicd-automationgit clone --depth 1 https://github.com/HermeticOrmus/claude-code-game-developmentWrote 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/hermeticormus/claude-code-game-development/cicd-automation)<a href="https://agentmods.dev/plugins/hermeticormus/claude-code-game-development/cicd-automation"><img src="https://agentmods.dev/badge/plugins/hermeticormus/claude-code-game-development/cicd-automation.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
cicd-automation 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 3d 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": "cicd-automation",
"source": "./plugins/cicd-automation",
"description": "CI/CD pipeline configuration, GitHub Actions/GitLab CI workflow setup, and automated deployment pipeline orchestration",
"version": "1.2.1",
"author": {
"name": "Seth Hobson",
"url": "https://github.com/wshobson"
},
"homepage": "https://github.com/wshobson/agents",
"repository": "https://github.com/wshobson/agents",
"license": "MIT",
"keywords": [
"ci-cd",
"automation",
"pipeline",
"github-actions",
"gitlab-ci"
],
"category": "infrastructure",
"strict": false,
"commands": [
"./commands/workflow-automate.md"
],
"agents": [
"./agents/deployment-engineer.md",
"./agents/devops-troubleshooter.md",
"./agents/kubernetes-architect.md",
"./agents/cloud-architect.md",
"./agents/terraform-specialist.md"
],
"skills": [
"./skills/deployment-pipeline-design",
"./skills/github-actions-templates",
"./skills/gitlab-ci-patterns",
"./skills/secrets-management"
]
}What it installs
The manifest is a name and a version. 4 skills travel with it, and installing the plugin installs all of them — 170 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside marketplace.json#cicd-automation 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.
- 3d ago First seen · 38 lines scan A e419b132b7f7
cicd-automation is a plugin published in the GitHub repository HermeticOrmus/claude-code-game-development (61 stars, last pushed 3mo 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
github-workflows
PR finalization (single, repo-wide, or org-wide including bots), repo refresh, rebase-merge, merge, review thread resolution, issue shaping, issue sweeping that reconciles open issues against reality, and diagnosing silent GitHub Actions failures.
pr-provenance-stamp
Embeds a reviewer-facing provenance receipt into your PR body when Claude runs gh pr create (or glab mr create). A PostToolUse hook (async, zero added latency) records a per-session ledger: tool calls, agent-authored lines, and every test/typecheck command with its real exit code; a PreToolUse (Bash) hook then rewr.
developer-essentials
Essential developer skills including Git workflows, SQL optimization, error handling, code review, E2E testing, authentication, debugging, and monorepo management.
charon
Ferries a GitHub PR to merge without waiting forever: an honest snapshot-not-block loop that fixes CI, repairs conflicts, version-checks reviewer suggestions, and never says 'just wait'.
beecount-release
BeeCount 全家桶发版流水线:双仓 tag 触发 CI、changelog 双格式、官网同步、视频文案收尾,带版本号与发布范围的用户确认门。.
release-please-monorepo
Set up automated semantic versioning, changelogs, and per-package publishing in a pnpm/Turbo monorepo using googleapis/release-please-action v4.