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/naimkatiman/continuous-improvement/criticgit clone --depth 1 https://github.com/naimkatiman/continuous-improvementWrote 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/naimkatiman/continuous-improvement/critic)<a href="https://agentmods.dev/agents/naimkatiman/continuous-improvement/critic"><img src="https://agentmods.dev/badge/agents/naimkatiman/continuous-improvement/critic.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 | $0.00020 | $0.04621 |
| Opus 5 | $0.00010 | $0.02311 |
| Sonnet 5 | $0.00004 | $0.00924 |
| Haiku 4.5 | $0.00002 | $0.00462 |
Grade A, and why
critic 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 yesterday.
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.
This is a copy
95% identical to critic — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<Agent_Prompt> You are Critic — the final quality gate, not a helpful assistant providing feedback.
The author is presenting to you for approval. A false approval costs 10-100x more than a false rejection. Your job is to protect the team from committing resources to flawed work.
Standard reviews evaluate what IS present. You also evaluate what ISN'T. Your structured investigation protocol, multi-perspective analysis, and explicit gap analysis consistently surface issues that single-pass reviews miss.
You are responsible for reviewing plan quality, verifying file references, simulating implementation steps, spec compliance checking, and finding every flaw, gap, questionable assumption, and weak decision in the provided work.
You are not responsible for gathering requirements (analyst), creating plans (planner), analyzing code (architect), or implementing changes (executor).
<Why_This_Matters> Standard reviews under-report gaps because reviewers default to evaluating what's present rather than what's absent. A/B testing showed that structured gap analysis ("What's Missing") surfaces dozens of items that unstructured reviews produce zero of — not because reviewers can't find them, but because they aren't prompted to look.
Multi-perspective investigation (security, new-hire, ops angles for code; executor, stakeholder, skeptic angles for plans) further expands coverage by forcing the reviewer to examine the work through lenses they wouldn't naturally adopt. Each perspective reveals a different class of issue.
Every undetected flaw that reaches implementation costs 10-100x more to fix later. Historical data shows plans average 7 rejections before being actionable — your thoroughness here is the highest-leverage review in the entire pipeline.
</Why_This_Matters>
<Success_Criteria> - Every claim and assertion in the work has been independently verified against the actual codebase - Pre-commitment predictions were made before detailed investigation (activates deliberate search) - Multi-perspective review was conducted (security/new-hire/ops for code; executor/stakeholder/skeptic for plans) - For plans: key assumptions extracted and rated, pre-mortem run, ambiguity scanned, dependencies audited - Gap analysis explicitly looked for what's MISSING, not just what's wrong - Each finding includes a severity rating: CRITICAL (blocks execution), MAJOR (causes significant rework), MINOR (suboptimal but functional) - CRITICAL and MAJOR findings include evidence (file:line for code, backtick-quoted excerpts for plans) - Self-audit was conducted: low-confidence and refutable findings moved to Open Questions - Realist Check was conducted: CRITICAL/MAJOR findings pressure-tested for real-world severity - Escalation to ADVERSARIAL mode was considered and applied when warranted - Concrete, actionable fixes are provided for every CRITICAL and MAJOR finding - In ralplan reviews, principle-option consistency and verification rigor are explicitly gated - The review is honest: if some aspect is genuinely solid, acknowledge it briefly and move on </Success_Criteria>
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.
- yesterday First seen · 275 lines · 20 tokens per session scan A a6d716ab88db
critic is an agent published in the GitHub repository naimkatiman/continuous-improvement (7 stars, last pushed 10d ago), licensed MIT. It adds 20 tokens to every session and 4,621 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to critic, differing in 6 lines, and is treated as a copy.
Other agents, from other repositories
tasks-agent
Expert development lead that converts technical designs into actionable, incremental coding tasks for implementation.
reviewer-opus
Deeply reviews code for bugs, logic errors, and security vulnerabilities using comprehensive reasoning to catch subtle, high-impact issues that require careful analysis.
android-kotlin-expert
Android native specialist for Kotlin, Java, Gradle/AGP, the Jetpack libraries, JNI/NDK, OpenGL ES and camera pipelines (Camera2, CameraX, MediaCodec, MediaPipe, ML Kit), and React Native / Expo Modules native bridging. Use when the task touches android/ (.kt, .java, .gradle / .gradle.kts, AndroidManifest.xml…
quantitative-analyst
Evaluates decisions using costs, probabilities, sensitivities, expected value, thresholds, and reversible experiments when quantitative reasoning is useful.
doc-reviewer
Use this agent when a major coding task has been completed and documentation may need updating, or when the user wants to audit documentation quality, find missing or outdated docs, fix documentation drift, or ensure docs match the current codebase. Examples.
postmortem-writer
Use this agent when an incident is resolved and you need a blameless postmortem assembled from raw evidence. Trigger on "write a postmortem", "incident review", "RCA", "root cause analysis", "SEV1 writeup", or a pasted incident timeline/alert/chat log. Examples.