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/rube-de/cc-skillsWrote 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/rube-de/cc-skills/ci-review)<a href="https://agentmods.dev/plugins/rube-de/cc-skills/ci-review"><img src="https://agentmods.dev/badge/plugins/rube-de/cc-skills/ci-review/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/rube-de/cc-skills/ci-review"><img src="https://agentmods.dev/badge/plugins/rube-de/cc-skills/ci-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ci-review 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 13d 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": "ci-review",
"description": "CI-optimized code review: multi-agent parallel review with confidence scoring and atomic GitHub PR review posting via gh api",
"author": {
"name": "rube-de",
"url": "https://github.com/rube-de"
}
}
What it installs
The manifest is a name and a version. 1 skill, 11 agents travel with it, and installing the plugin installs all of them — 559 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill ci-review A 127 tokens
- Agent bug-detector A 42 tokens
- Agent confidence-scorer A 40 tokens
- Agent deep-reviewer A 39 tokens
- Agent silent-failure-hunter A 38 tokens
- Agent single-reviewer A 42 tokens
- Agent code-simplifier A 34 tokens
- Agent comment-analyzer A 39 tokens
- Agent guidelines-checker A 37 tokens
- Agent security-reviewer A 39 tokens
- Agent test-analyzer A 43 tokens
- Agent type-analyzer A 39 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.
- 13d ago Changed · +3 lines 1f80f63505a2
- 1mo ago First seen · 6 lines scan A f618383e60b1
ci-review is a plugin published in the GitHub repository rube-de/cc-skills (10 stars, last pushed today), 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
han-github
Github specific extensions to the Han plugin for agentic planning and coding. Provides skills to post code reviews as PR comments, update a PR description with a consistent format, etc.
gerrit
An MCP server for interacting with the Gerrit code review system.
odin-git
ODIN workflows for commits, branches, pull requests, review feedback, and issue tracking.
open-pr
Pre-flight checks and PR creation workflow: run tests, open a PR, code review, and check CI.
pr-trains
Batch operators for GitHub queues: review-train reviews every open PR, fix-train applies requested changes, fix-ci-train turns red CI green, merge-train fixes and merges in dependency order, issue-train triages and builds one PR per actionable issue — all with parallel sub-agents and one grouped confirmation.
agent-traffic-control
Coordination toolkit for parallel Claude Code sessions sharing one repo — issue-pickup claim protocol (assignee + wip label), worktree & session-isolation pitfalls, parallel-PR conflict recovery, subagent-integrity edge cases, and squash/merge mechanics for parallel-PR workflows. Plus two opt-in hooks: leg-guard…