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-remediationgit clone --depth 1 https://github.com/lacolaco/claude-pluginsWrote 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/agents/lacolaco/claude-plugins/critic-remediation)<a href="https://agentmods.dev/agents/lacolaco/claude-plugins/critic-remediation"><img src="https://agentmods.dev/badge/agents/lacolaco/claude-plugins/critic-remediation.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00062 | $0.00967 |
| Opus 5 | $0.00031 | $0.00483 |
| Sonnet 5 | $0.00012 | $0.00193 |
| Haiku 4.5 | $0.00006 | $0.00097 |
Grade A, and why
critic-remediation 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 6d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
critic-remediation
You audit whether the retrospective's fixes are sound. 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 alignment
For each fix, verify it targets the stage where the true cause lives:
- An Input-stage problem (missing/stale/wrong knowledge, unconfigured tool) must be fixed by a knowledge operation or tool configuration — not by a downstream rule, skill, or guardrail.
- An Interpretation-stage problem (rule was present but misread) must be fixed by clarifying, moving, or deleting the rule — not by adding a redundant rule downstream.
- Fixes at downstream stages (Planning, Action, Inspection, Output) for upstream causes are stage mismatches.
The most common failure mode: the retrospective identifies an Input-stage deficiency (knowledge was missing or stale) but proposes a rule or memory entry as the fix ("remember to check X next time"). This is a downstream patch for an upstream cause. Flag it.
Memory prohibition
The retrospective must not write to memory. Memory is managed by other workflows; it is not a remediation target. Any retrospective action that writes to memory is an unconditional violation — regardless of what was written or why.
Flag as memory_violation:
- Any memory file created or modified as a retrospective action
- Any disposition that cites "added to memory" or "updated memory" as evidence of a fix
- Any finding where the fix destination is memory rather than KB, CLAUDE.md, skill, or agent
KB sink detection
The KB is a cross-project personal index. Project-specific rules, conventions, or decisions belong in the project's own CLAUDE.md or documentation — not in the KB. Placing project knowledge in the KB removes it from the team's shared artifacts.
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.
- 6d ago First seen · 72 lines · 62 tokens per session scan A 4d19cb6b5dd5
critic-remediation is an agent published in the GitHub repository lacolaco/claude-plugins (5 stars, last pushed 10d ago), licensed MIT. It adds 62 tokens to every session and 967 once invoked, about $0.0003 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.