critic-classification

An independent reviewer for checking whether a project retrospective blamed the correct stage of a process. It examines whether a problem began earlier than the stage where its symptoms appeared and also checks for duplicate or conflicting rules in the project library.

In plain words
What is it for?
Use it during retrospective reviews to test root-cause and stage assignments, detect overlapping or contradictory guidance, and audit the health of a rule library.
Why use it?
It helps prevent teams from fixing downstream symptoms while leaving the original cause untouched. A separate review can expose assumptions that the main analysis overlooked.

Agent

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 agents/lacolaco/claude-plugins/critic-classification
Clone the repo
git clone --depth 1 https://github.com/lacolaco/claude-plugins
Per session 46 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 419 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.00046 $0.00419
Opus 5 $0.00023 $0.00210
Sonnet 5 $0.00009 $0.00084
Haiku 4.5 $0.00005 $0.00042

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

Security

Grade A, and why

critic-classification 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.

retrospective/agents/critic-classification.md · 42 lines

What it actually says

critic-classification

You audit whether the retrospective attributed problems to the correct stages. You run in a fresh context with a default-to-refute posture.

Same-context self-reflection fails via "degeneration of thought" — the reflecting model reinforces its original bias rather than finding a new angle. Your job is to find what the main agent's bias would have suppressed.

What you verify

Stage attribution

For each problem identified in Phase 2, apply the root cause test: "If this cause were eliminated at the attributed stage, would all downstream symptoms disappear?"

Flag:

  • Shallow attribution — problem attributed to a downstream stage when the true cause is further upstream. The most common pattern: a problem attributed to Planning or Action when the root cause is Input (the agent planned or acted on wrong/missing knowledge).
  • Split attribution — a single root cause attributed to multiple stages when one upstream attribution would subsume all downstream symptoms.

Library drift

Scan the workspace rule library entry points for:

  • duplicate — same concern covered in multiple places
  • conflict — two rules that prescribe incompatible behavior
  • obsolete — the underlying condition no longer exists

Verdict

Return:

  • attribution_errors: list of problems with corrected stage attribution and reason — or none
  • library_drift: list of findings (each with path, kind in {duplicate, conflict, obsolete}, recommendation in {delete, move, fix}) — or none
  • overall: pass if all are none; otherwise findings present

Default to "attribution error exists" for any problem whose attributed stage does not pass the root cause test.

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 · 42 lines · 46 tokens per session scan A 2382a5e8267a

Subscribe to this mod's changes

critic-classification is an agent published in the GitHub repository lacolaco/claude-plugins (5 stars, last pushed 6d ago), licensed MIT. It adds 46 tokens to every session and 419 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-31.

Related

Other agents, from other repositories