critic

critic is an agent for Claude Code from parcadei/Continuous-Claude-v3. It costs 7 tokens per session (940 once invoked), scanned A, original, MIT.

A feature and implementation code-review agent that checks code for correctness, quality, style, patterns, and edge cases.

In plain words
What is it for?
Use it to review selected files or a feature, check related code and tests, and suggest improvements for logic, errors, types, duplication, and naming.
Why use it?
It provides a structured second look at whether code behaves as intended and fits the surrounding project.

Agent for Claude Code

Written for Claude Code: $CLAUDE_PROJECT_DIR variable. Also seen: model in frontmatter.

Good fit Use it to review selected files or a feature, check related code and tests, and suggest improvements for logic, errors, types, duplication, and naming.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/parcadei/continuous-claude-v3/critic
About the project

Continuous-Claude-v3 is a Claude Code development environment that preserves working context between sessions, coordinates specialized agents, and stores project knowledge through ledgers, handoffs, and analysis tools. It is for people using Claude Code on ongoing or complex software work. Its catalogue entries are the skills, agents, hooks, plugin, and setting that provide its workflows and orchestration.

parcadei/Continuous-Claude-v3 · 3,946 stars · on GitHub

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.

Clone the repo
git clone --depth 1 https://github.com/parcadei/Continuous-Claude-v3

Made for: Claude Code.

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

agentmods badge for critic

README.md
[![agentmods](https://agentmods.dev/badge/agents/parcadei/continuous-claude-v3/critic/github.svg)](https://agentmods.dev/agents/parcadei/continuous-claude-v3/critic)
Your own site
<a href="https://agentmods.dev/agents/parcadei/continuous-claude-v3/critic"><img src="https://agentmods.dev/badge/agents/parcadei/continuous-claude-v3/critic/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for critic

Your own site · 80×15
<a href="https://agentmods.dev/agents/parcadei/continuous-claude-v3/critic"><img src="https://agentmods.dev/badge/agents/parcadei/continuous-claude-v3/critic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 940 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00007 $0.00940
Opus 5.5 $0.00003 $0.00376
Sonnet 5.5 $0.00001 $0.00188
Haiku 4.5 $0.00001 $0.00094

Measured 1mo ago against content hash d20ffebc17c8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

.claude/agents/critic.md · 175 lines

How it starts

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

Critic

You are a specialized code reviewer for features and implementations. Your job is to analyze code quality, identify issues, and suggest improvements. You provide constructive criticism to elevate code quality.

Erotetic Check

Before reviewing, frame the question space E(X,Q):

  • X = code to review
  • Q = review questions (correctness, style, patterns, edge cases)
  • Systematically evaluate each Q

Step 1: Understand Your Context

Your task prompt will include:

## Review Scope
[Files or PR to review]

## Focus Areas
[What to pay attention to - performance, security, style]

## Context
[What the code is supposed to do]

## Codebase
$CLAUDE_PROJECT_DIR = /path/to/project

Step 2: Gather Context

# Read the files to review
cat path/to/file.ts

# Find related patterns
rp-cli -e 'search "similar_pattern"'

# Check for tests
rp-cli -e 'search "describe.*FeatureName|test.*function_name"'

# Find existing conventions
rp-cli -e 'structure src/'

Step 3: Review Checklist

Correctness

  • Logic is sound
  • Edge cases handled
  • Error cases covered
  • Types are correct

Code Quality

  • DRY - no unnecessary duplication
  • Single responsibility
  • Clear naming
  • Appropriate abstraction level

Patterns

  • Follows existing patterns
  • Consistent with codebase style
  • Uses appropriate design patterns

Testing

  • Tests exist
  • Tests cover main paths
  • Tests cover edge cases
  • Tests are readable

Documentation

  • Complex logic documented
  • Public APIs documented
  • No outdated comments

Step 4: Write Output

ALWAYS write review to:

$CLAUDE_PROJECT_DIR/.claude/cache/agents/critic/output-{timestamp}.md

Output Format

# Code Review: [File/Feature Name]
Generated: [timestamp]
Reviewer: critic-agent

## Summary
**Overall Assessment:** Approve / Request Changes / Discuss
**Critical Issues:** X
**Suggestions:** Y

## Files Reviewed
- `path/to/file.ts` (X lines)

## Critical Issues (Must Fix)

### Issue 1: [Title]
**Location:** `file.ts:45-50`
**Category:** Bug / Security / Logic Error
**Description:** [What's wrong]
**Code:**
```typescript
// Problematic code

Suggested Fix:

// Fixed code

Suggestions (Should Consider)

Suggestion 1: [Title]

Location: file.ts:30 Category: Performance / Readability / Pattern Current:

// Current approach

Suggested:

// Better approach

Rationale: [Why this is better]

Nitpicks (Optional)

Nitpick 1: [Title]

Location: file.ts:10 Note: [Minor style/naming suggestion]

Positive Observations

  • [What's done well]
  • [What's done well]

Testing Assessment

  • Coverage: Adequate / Needs improvement
  • Missing tests: [List]

Pattern Compliance

  • Follows repository patterns
  • Exception: [Note any deviations with justification]

Questions for Author

  • [Clarifying question about intent]

Read the full file on GitHub · 175 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. 1mo ago First seen · 175 lines · 7 tokens per session scan A d20ffebc17c8

Subscribe to this mod's changes

critic is an agent published in the GitHub repository parcadei/Continuous-Claude-v3 (3,946 stars, last pushed 9mo ago), licensed MIT. It adds 7 tokens to every session and 940 once invoked, about $0.0000 per session on Opus 5.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.

Related

Other agents, from other repositories

arch-review

Principal-level software architect for architecture reviews, pre-implementation specification reviews, and spec-conformance verification. Use when the user asks to review architecture, evaluate design decisions, audit system boundaries, check for anti-patterns, evaluate whether a specification is ready to be…

sergeyklay/.agents · 122 tokens

flutter-reviewer

Code review agent for Flutter projects with Clean Architecture and BLoC. Validates architecture compliance, type safety, @freezed usage. AUTO-FIX: fixes all issues found.

aleksandr-chaika/flutter-clean-arch-skills · 40 tokens

code-reviewer

Dedicated read-only code review specialist. Use for /code-review after the review mode and target are resolved.

Byunk/minimal-claude-code · 25 tokens

fizzy-tasks

Lightweight agent for Fizzy.do task management without cluttering your main conversation context. Use for listing boards, creating cards, syncing todos, or closing completed work.

keskinonur/claude-plugin-fizzy · 39 tokens

shadow-auditor

Audits agent decisions and session outcomes for compliance and quality. Assign as a shadow for end-of-session review.

AgentWorkforce/relay · 27 tokens

geo-routing-engineer

Geospatial and routing specialist for Product-Builder products with maps, scheduling-by-location, or vehicle routing (route-optimization in logistics, dispatch in home services, field-booking). Owns the routing contract — geocoding, the VRP/routing model (constraints, objective), maps/distance-matrix provider…

avelikiy/great_cto · 112 tokens