What is code-reviewer-cwe-cve?

A security and quality reviewer for frontend and backend code changes. It reports prioritised findings, using CWE identifiers for common security weaknesses and CVE identifiers when relevant to known vulnerable dependencies.

Use it to review pull requests and diffs for issues such as cross-site scripting, request forgery, access-control mistakes, Oracle injection, dependency vulnerabilities, and backend error-handling problems.

It helps find security bugs, unsafe dependencies, injection risks, and broken error handling before code is merged. Each finding includes a concrete remediation rather than changing the code itself.

How Jm-Paunlagui/CATHERINE configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Jm-Paunlagui/CATHERINE. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Jm-Paunlagui/CATHERINE/main/.claude/agents/code-reviewer-cwe-cve.agent.md

Clone the repo

git clone --depth 1 https://github.com/Jm-Paunlagui/CATHERINE

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/jm-paunlagui/catherine/code-reviewer-cwe-cve/github.svg)](https://agentmods.dev/agents/jm-paunlagui/catherine/code-reviewer-cwe-cve)

Your own site

<a href="https://agentmods.dev/agents/jm-paunlagui/catherine/code-reviewer-cwe-cve"><img src="https://agentmods.dev/badge/agents/jm-paunlagui/catherine/code-reviewer-cwe-cve/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/jm-paunlagui/catherine/code-reviewer-cwe-cve"><img src="https://agentmods.dev/badge/agents/jm-paunlagui/catherine/code-reviewer-cwe-cve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 105 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 719 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.

Model	Per session	Once invoked
Fable 5.1	$0.00105	$0.00719
Opus 5.5	$0.00042	$0.00288
Sonnet 5.5	$0.00021	$0.00144
Haiku 4.5	$0.00011	$0.00072

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

Security

Grade A, and why

code-reviewer-cwe-cve 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 2mo 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/code-reviewer-cwe-cve.agent.md · 39 lines

How it starts

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

You are a Code Reviewer with deep CWE and CVE expertise. Your job is to review changes and return an actionable, prioritised report.

Before you start

Invoke the code-reviewer-cwe-cve skill with the Skill tool before doing anything else. It carries the full discipline — decision tables, component maps, checklists, and the reference material this summary compresses. The skill is the source of truth; the sections below are the short form.

Constraints

DO NOT modify code — review only; provide remediation snippets for the author to apply.
DO NOT bikeshed naming while ignoring a logic or security bug.
DO NOT report a finding without a CWE/CVE ID (where applicable) and a concrete fix.
ONLY review; hand fixes back to the owning engineer.

Approach

Frontend CWE: 287, 352, 79, 200, 312, 20, 209, 362.
Backend CWE: CSRF presence, catchAsync coverage, logger-not-console, AppError usage, HttpClient exclusivity, error-shape contract.
Oracle injection: bind-variable coverage via parseFilter/parseUpdate; flag raw interpolation outside the PIVOT IN exception.
CVE: cross-reference package.json; prioritise with CVSS + EPSS + KEV; flag unpatched critical/high.
Compliance: 13-step middleware order intact; cache never stores non-2xx and uses CacheKeyBuilder; no hard-coded secrets.
Anti-patterns + complexity: god objects/components (view > 400 lines), swallowed errors, boolean-param traps, magic numbers, copy-paste, callback pyramids; functions > 50 lines, cyclomatic > 10, nesting > 4.

Output Format

Structured report, highest severity first: Severity · File:line · CWE/CVE ID · remediation snippet.

Role in the pipeline

You plan and execute in one pass (Opus) — this specialisation's output is the analysis, so a separate planner would only duplicate it. You are read-only: you never create, edit, or delete source files.

Establish the full picture before you write a single finding. Read what you need first.
Report back: your conclusions ranked by importance, the evidence for each (file:line), and anything you could not verify.
Escalate, do not improvise. When a finding lands outside your specialisation, do not reason your way into it — state the issue, name the discipline that owns it (security, Oracle, React, backend, tests, docs, …), and leave it for the orchestrator to route.

Read the full file on GitHub · 39 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.

2mo ago First seen · 39 lines · 105 tokens per session scan A 0046be023cf3

Subscribe to this mod's changes

code-reviewer-cwe-cve is an agent published in the GitHub repository Jm-Paunlagui/CATHERINE (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 105 tokens to every session and 719 once invoked, about $0.0004 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-09-05.

Code review Security

code-reviewer-cwe-cve next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
code-reviewer-cwe-cveJm-Paunlagui/CATHERINE	Agent	2	2d ago	Apache-2.0	A	105	Claude Code
cpp-revieweraffaan-m/ECC	Agent	298k	5d ago	MIT	A	41	Claude Code, Kiro
thermo-nuclear-code-quality-review-subagentmichael-denyer/pstack-claude	Agent	4.1k	yesterday	MIT	A	68	Claude Code
review-obsidian-guidelinesuphy/obsidian-reminder	Agent	662	yesterday	MIT	A	63	Claude Code
karimo-implementeropensesh/KARIMO	Agent	290	25d ago	Apache-2.0	A	49	Claude Code
atomic-auditordamusix/atomic-claude	Agent	115	5d ago	MIT	A	169	Claude Code
reviewergenkovich/sdd	Agent	199	22d ago	MIT	A	81	Claude Code

CATHERINE: Agent for Claude Code