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 AIops-tools/CICD-AIopsnpx agentmods add plugins/aiops-tools/cicd-aiops/cicd-aiopsgit clone --depth 1 https://github.com/AIops-tools/CICD-AIopsWrote 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/aiops-tools/cicd-aiops/cicd-aiops)<a href="https://agentmods.dev/plugins/aiops-tools/cicd-aiops/cicd-aiops"><img src="https://agentmods.dev/badge/plugins/aiops-tools/cicd-aiops/cicd-aiops.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
cicd-aiops 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
{
"$schema": "https://anthropic.com/claude-code/plugin.schema.json",
"name": "cicd-aiops",
"displayName": "CICD AIops",
"version": "0.9.0",
"description": "Governed self-managed GitLab + Gitea CI/CD ops: pipelines, runners, artifacts, RCA. 28 tools.",
"author": {
"name": "Wei Zhou",
"email": "[email protected]",
"url": "https://github.com/AIops-tools"
},
"homepage": "https://github.com/AIops-tools/CICD-AIops",
"repository": "https://github.com/AIops-tools/CICD-AIops",
"license": "MIT",
"keywords": [
"aiops",
"mcp",
"governance",
"cicd"
]
}
What it installs
The manifest is a name and a version. 1 skill, 1 MCP server travel with it, and installing the plugin installs all of them — 324 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 22 lines scan A 5b811458e20f
cicd-aiops is a plugin published in the GitHub repository AIops-tools/CICD-AIops (0 stars, last pushed 8d 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-31.
Other plugins, from other repositories
jenkins-cli
GitHub CLI-style interface for Jenkins controllers - create multibranch jobs, inspect config.xml, and manage runs, logs, artifacts, credentials, nodes, and queues.
go-ultimate
Opinionated Go development skill — architecture, conventions, production readiness, repo/CI hygiene, review, and MCP/agent patterns.
codeql-resolver
Systematic CodeQL alert analysis and resolution for GitHub Actions workflows.
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'.
craft
Full-stack developer toolkit with integrated workflow automation - 48 commands, 2 agents, 41 skills with standardized dry-run preview mode (29 with --dry-run support). Code, git, site, docs, testing, architecture, CI, distribution, teaching workflows, planning, release pipeline, and ADHD-friendly features including…
release-please-monorepo
Set up automated semantic versioning, changelogs, and per-package publishing in a pnpm/Turbo monorepo using googleapis/release-please-action v4.