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/jhoblitt/rook-claudeWrote 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/jhoblitt/rook-claude/rook-maintainer)<a href="https://agentmods.dev/plugins/jhoblitt/rook-claude/rook-maintainer"><img src="https://agentmods.dev/badge/plugins/jhoblitt/rook-claude/rook-maintainer/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/jhoblitt/rook-claude/rook-maintainer"><img src="https://agentmods.dev/badge/plugins/jhoblitt/rook-claude/rook-maintainer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
rook-maintainer 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 yesterday.
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": "rook-maintainer",
"displayName": "Rook Maintainer",
"version": "0.25.3",
"description": "Maintainer-grade skills for rook (github.com/rook/*): code review, backlog triage, systemic-PR campaigns, and the rook house conventions they enforce",
"author": {
"name": "Joshua Hoblitt",
"email": "[email protected]",
"url": "https://github.com/jhoblitt"
},
"homepage": "https://github.com/jhoblitt/rook-claude",
"repository": "https://github.com/jhoblitt/rook-claude",
"license": "Apache-2.0",
"keywords": [
"rook",
"ceph",
"kubernetes",
"code-review",
"triage"
]
}
What it installs
The manifest is a name and a version. 5 skills, 5 agents, 2 hooks travel with it, and installing the plugin installs all of them — 724 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill rook-code-review A 116 tokens
- Skill rook-triage A 118 tokens
- Skill rook-conventions A 85 tokens
- Skill rook-pr-takeover A 0 tokens
- Skill rook-systemic-prs C 104 tokens
- Agent rook-reviewer A 68 tokens
- Agent design-attacker A 99 tokens
- Agent code-worker A 28 tokens
- Agent rook-triager B 58 tokens
- Agent kb-resolver C 48 tokens
- Hook UserPromptSubmit A not measured
- Hook PreToolUse A not measured
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.
- yesterday Changed 8a2839026056
- 1mo ago Changed f70f0b6822d3
- 1mo ago Changed c903d54e51c5
- 1mo ago Changed 19eb79e6162c
- 1mo ago Changed c6588ce290f6
- 1mo ago First seen · 22 lines scan A e40c99b5e670
rook-maintainer is a plugin published in the GitHub repository jhoblitt/rook-claude (4 stars, last pushed yesterday), licensed Apache-2.0. 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
revenue
Outbound, sales enablement, revenue operations, pricing and packaging, activation, retention, and referrals.
ring-pm-team
Pre-dev planning workflows: 4-gate and 8-gate orchestrators for PRD, TRD, OpenAPI contracts, schema design, and a phased plan. 14 skills + 4 research agents.
nid-team
NI&D team PR triage and review workflow tools.
cadence
A plan/execute/verify loop for a single developer in Claude Code, with adversarial review at every gate: plans and diffs get refuted by a fresh Claude subagent or a panel of outside models (OpenAI, Gemini, DeepSeek), not just approved. State lives in files, not the conversation, so you clear aggressively and keep both.
dev-mcp
Narzedzia deweloperskie MateMatic (advanced): spec-driven development, kanon budowy MCP serverow, recenzent PR dla LegalTech AI, generator instalatora marketplace. Bez konektorow.
milestone-driver
Drives a GitHub milestone to completion: triages each issue for design gaps + dependency order up front, then for each buildable issue finds the root cause (or parks it), dispatches a TDD implementer subagent, runs unit + E2E tests + code review, opens a PR, and auto-merges issues on CI green. The whole loop sits…