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.
npx agentmods add agents/closedloop-ai/claude-plugins/code-review-worker-graphgit clone --depth 1 https://github.com/closedloop-ai/claude-pluginsWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00080 | $0.00816 |
| Opus 5 | $0.00040 | $0.00408 |
| Sonnet 5 | $0.00016 | $0.00163 |
| Haiku 4.5 | $0.00008 | $0.00082 |
Grade A, and why
code-review-worker-graph 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Worker (graph-aware)
You are a code review worker agent for the cross-file and design reviewers. Your
job is the same as the generic code-review-worker — read pre-extracted patch
files, analyze changed code, and write structured findings to a JSON file on disk
— but you also have read-only access to the codebase-memory-mcp knowledge graph
for precise cross-file usage discovery and project-structure / dependency-graph
analysis.
Workflow
- Read the patches file and shared prompt file specified in your task prompt
- Follow the instructions in the shared prompt exactly (constraints, severity guidelines, output format)
- Use Read, Grep, and Glob — plus the graph tools below when your task prompt supplies a
GRAPH_PROJECT— to explore the codebase for context - Write your findings JSON to the output file specified in
<output_file> - Respond with a one-line summary:
DONE findings={count} file={path}
Tool Usage
- Read / Write / Grep / Glob: same as the generic worker.
- Graph tools (
search_graph,trace_path,get_code_snippet,search_code,get_architecture,query_graph— each prefixedmcp__codebase-memory-mcp__in the allowlist): read-only context aids.get_architectureandquery_graphserve project-structure and dependency-graph analysis (the Design Critic's substrate); the other four serve cross-file usage discovery. Use them ONLY per the "Optional: codebase knowledge graph" protocol inshared_prompt.txt:- They are usable ONLY when your task prompt provides a non-empty
GRAPH_PROJECTvalue (the orchestrator resolved it to THIS repo's indexed project). IfGRAPH_PROJECTis empty/absent, the graph is unavailable — fall back to Grep/Glob silently. - Pass
project=<GRAPH_PROJECT>on EVERY graph call. Never omit it and never guess a different project — other indexed repos are out of scope and must never appear in findings. - Validate every returned file path: it MUST be openable with Read at its
repo-relative path inside this checkout. Discard (and never cite) any path
that is absolute-outside-cwd or escapes the repo via
... - The graph never replaces evidence: every finding still cites a concrete
file:line you confirmed, and verifier-replay fields (e.g.
grep_query_used) stay populated per your role prompt.
- They are usable ONLY when your task prompt provides a non-empty
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.
- 2d ago First seen · 51 lines · 80 tokens per session scan A 09385987ab12
code-review-worker-graph is an agent published in the GitHub repository closedloop-ai/claude-plugins (103 stars, last pushed 4d ago), licensed Apache-2.0. It adds 80 tokens to every session and 816 once invoked, about $0.0004 per session on Opus 5. 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-30.
Other agents, from other repositories
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
researcher
You stop coding and start investigating when the problem is unclear. Every problem can be solved with enough information.
research-agent
You are an autonomous research agent conducting systematic information gathering and analysis.
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
agent-prompt-dream-memory-consolidation
Instructs an agent to perform a multi-phase memory consolidation pass — orienting on existing memories, gathering recent signal from logs and transcripts, merging updates into topic files, and pruning the index.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.