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/lacolaco/claude-plugins/critic-classificationgit clone --depth 1 https://github.com/lacolaco/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.00046 | $0.00419 |
| Opus 5 | $0.00023 | $0.00210 |
| Sonnet 5 | $0.00009 | $0.00084 |
| Haiku 4.5 | $0.00005 | $0.00042 |
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.
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 — ornonelibrary_drift: list of findings (each withpath,kindin {duplicate, conflict, obsolete},recommendationin {delete, move, fix}) — ornoneoverall:passif all arenone; otherwisefindings present
Default to "attribution error exists" for any problem whose attributed stage does not pass the root cause test.
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 · 42 lines · 46 tokens per session scan A 2382a5e8267a
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.
Other agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
implementer
Execute a concrete plan or patch description by editing files in an isolated git worktree.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
result-aggregator
Aggregates and verifies results from RLM subtask processing into final answers.