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/nodnarbnitram/claude-code-extensionsWrote 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/nodnarbnitram/claude-code-extensions/cce-devops)<a href="https://agentmods.dev/plugins/nodnarbnitram/claude-code-extensions/cce-devops"><img src="https://agentmods.dev/badge/plugins/nodnarbnitram/claude-code-extensions/cce-devops.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
cce-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 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": "cce-devops",
"version": "1.0.0",
"description": "DevOps tooling: GitHub Actions, Helm, ArgoCD, and Crossplane for CI/CD and infrastructure",
"author": {
"name": "Claude Code Extensions Contributors",
"url": "https://github.com/nodnarbnitram/claude-code-extensions"
},
"homepage": "https://github.com/nodnarbnitram/claude-code-extensions",
"repository": "https://github.com/nodnarbnitram/claude-code-extensions",
"license": "MIT",
"keywords": [
"devops",
"ci-cd",
"github-actions",
"helm",
"argocd",
"crossplane"
]
}
What it installs
The manifest is a name and a version. 8 agents travel with it, and installing the plugin installs all of them — 499 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Agent argocd-operator-expert A 52 tokens
- Agent argocd-user-expert A 55 tokens
- Agent crossplane-upgrade-agent A 47 tokens
- Agent helm-template-master A 53 tokens
- Agent crossplane-aws-rds-expert A 95 tokens
- Agent github-actions-expert A 61 tokens
- Agent helm-argocd-applicationset-expert A 67 tokens
- Agent argocd-developer-expert B 69 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.
- 3d ago First seen · 21 lines scan A c773215191e1
cce-devops is a plugin published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 4mo 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
devops-pipeline
CI/CD automation — git worktrees, deploy pipeline, canary monitoring, auto-format/test hooks, and GitHub Actions templates.
nyann
Project governance for Claude Code. Bootstrap and maintain git workflow, hooks, commits, releases, CI, docs, and repo health.
aio-devops
GitHub, GitLab, and git worktree workflows in one toolkit — manage repos, PRs, MRs, pipelines, and parallel branches without juggling CLIs.
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'.
socket-release
Stand up SocketDev publishing (npm, crates.io, GitHub releases, Homebrew tap) in a repo: copy in the release kit and run its bootstrap - name reservation, GitHub environments, npm trusted publisher, staged publish config, verification.
beecount-release
A release workflow for BeeCount projects that coordinates version tags, change logs, website updates and video copy across two code repositories. A release is the process of publishing a new software version.