deep

A command for a deeper code review that adds design and change-impact checks to the standard reviewer group. It examines software structure and changes to exported code symbols.

In plain words
What is it for?
Use it when a change needs checks for module boundaries, dependency direction, SOLID principles, project structure, and possible impact on code used elsewhere.
Why use it?
It helps identify design problems and effects on other code that a basic review may miss.

Command

Install

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.

agentmods
npx agentmods add commands/closedloop-ai/claude-plugins/deep
Clone the repo
git clone --depth 1 https://github.com/closedloop-ai/claude-plugins
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,054 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5 $0.00030 $0.01054
Opus 5 $0.00015 $0.00527
Sonnet 5 $0.00006 $0.00211
Haiku 4.5 $0.00003 $0.00105

Measured 2d ago against content hash 763b1b8ed13d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

deep 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.

plugins/code-review/commands/deep.md · 46 lines

How it starts

The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Deep Code Review (PLN-807 + FEA-1401)

This command is shorthand for /start --depth deep. Follow every instruction in ${CLAUDE_PLUGIN_ROOT}/commands/start.md verbatim, with one binding:

DEPTH = "deep" for the entire run. Pass --depth deep to every helper that accepts the flag (notably prepare-run, hygiene, review-state-read, and review-state-write).

What deep does

Deep produces the standard fleet plus two deep-only conditional core reviewers: the always-on Design Critic and the signal-gated Impact Analyzer (FEA-1401).

The Design Critic runs on every deep review (no trigger required). It evaluates the change for software-design craftsmanship — module depth and information hiding, SOLID adherence, dependency direction and layer boundaries, and project/package structure — drawing on A Philosophy of Software Design, the SOLID principles, and Clean Architecture. It flags only design flaws this change introduces or demonstrably worsens (a new shallow module, a wrong-direction dependency, a god-class this PR grew, a type-switch it extended), runs on Sonnet, and is exempt from the domain-critic cap (it is a source: "core" reviewer, not a project-specific critic). Like the Impact Analyzer it is graph-aware: when the repo is indexed it queries the codebase-memory-mcp knowledge graph (get_architecture for module/layer layout, query_graph for dependency direction and import cycles), falling back to grep otherwise. Findings carry category: "Code Quality".

The Impact Analyzer (FEA-1401) spawns when signal extraction detects exported_symbol_change or symbol_deletion in the diff. It identifies changed exported symbols (function signatures, type definitions, exported constants, class API, schema fields, deletions), greps the codebase for external usages outside the diff, and emits findings whose external_impact[] array lists every callsite that breaks under the new signature.

Component shallow standard deep
All standard reviewers (subset)
Domain critics (from critic-gates.json) ✓ (≤3) ✓ (≤3)
Design Critic ✓ (always)
Impact Analyzer (FEA-1401) ✓ (when triggered)

Read the full file on GitHub · 46 lines

Changes

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.

  1. 2d ago First seen · 46 lines · 30 tokens per session scan A 763b1b8ed13d

Subscribe to this mod's changes

deep is a command published in the GitHub repository closedloop-ai/claude-plugins (103 stars, last pushed 4d ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,054 once invoked, about $0.0002 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.