dev-mcp-tools: Agent for Claude Code

.claude/agents/code-review-gate.md

code-review-gate is an agent for Claude Code from brianmontero18/dev-mcp-tools. It costs 24 tokens per session (342 once invoked), scanned A, original, MIT.

A final code review assistant for changes about to be submitted or merged. It checks correctness, security, accessibility, performance, types, tests, and Storybook coverage.

In plain words
What is it for?
Use it to review pull-request changes, identify critical issues and warnings, suggest small fixes, and list commands for checking the result locally.
Why use it?
It helps catch problems such as exposed secrets, broken user flows, missing error handling, inaccessible controls, unnecessary re-rendering, and weak tests before a change reaches the main codebase.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

This is brianmontero18/dev-mcp-tools's own configuration. It tells Claude Code how to work on dev-mcp-tools itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything dev-mcp-tools configures →

Reuse

Borrowing it

Nothing to install: this file belongs to brianmontero18/dev-mcp-tools. 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/brianmontero18/dev-mcp-tools/main/.claude/agents/code-review-gate.md
Clone the repo
git clone --depth 1 https://github.com/brianmontero18/dev-mcp-tools

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 code-review-gate

README.md
[![agentmods](https://agentmods.dev/badge/agents/brianmontero18/dev-mcp-tools/code-review-gate/github.svg)](https://agentmods.dev/agents/brianmontero18/dev-mcp-tools/code-review-gate)
Your own site
<a href="https://agentmods.dev/agents/brianmontero18/dev-mcp-tools/code-review-gate"><img src="https://agentmods.dev/badge/agents/brianmontero18/dev-mcp-tools/code-review-gate/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 code-review-gate

Your own site · 80×15
<a href="https://agentmods.dev/agents/brianmontero18/dev-mcp-tools/code-review-gate"><img src="https://agentmods.dev/badge/agents/brianmontero18/dev-mcp-tools/code-review-gate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 342 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.00024 $0.00342
Opus 5.5 $0.00010 $0.00137
Sonnet 5.5 $0.00005 $0.00068
Haiku 4.5 $0.00002 $0.00034

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

Security

Grade A, and why

code-review-gate 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-review-gate.md · 35 lines

What it actually says

Role

You are the last reviewer. You catch correctness, security, and UX/a11y issues and propose minimal, high-leverage fixes.

Objectives

  • Ensure readability, error handling, no secrets, and a11y compliance.
  • Verify type safety and basic performance hygiene (avoid needless re-renders).
  • Check test adequacy (RTL/MSW) and story coverage (Chromatic).

Constraints & Guardrails

  • Do not bikeshed style if format/lint pass; focus on correctness and UX risks.
  • Prefer small diffs; suggest code snippets that can be applied safely.

Tools Policy

  • Use Grep/Glob/Read to inspect diffs and touched files.
  • Use Bash only for format/lint/typecheck/test commands.

Review Checklist

  • Critical: secrets, security, broken flows, wrong types.
  • A11y/UX: roles/labels/keyboard; loading/error states.
  • Perf: heavy renders, missing memoization where obvious.
  • Tests/Stories: sufficient RTL/MSW; stories for key states.
  • GraphQL: typed hooks, fragments, sane cache.

Output Format

  • Critical Issues (must fix) with code suggestions.
  • Warnings (should fix) with rationale.
  • Nice-to-haves with examples.
  • Commands to re-check locally.
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. 2mo ago First seen · 35 lines · 24 tokens per session scan A 20ee2c99311e

Subscribe to this mod's changes

code-review-gate is an agent published in the GitHub repository brianmontero18/dev-mcp-tools (0 stars, last pushed 1y ago), licensed MIT. It adds 24 tokens to every session and 342 once invoked, about $0.0001 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-01.

Related

Other agents, from other repositories

cpp-reviewer

Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.

affaan-m/ECC · 41 tokens

thermo-nuclear-code-quality-review-subagent

Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.

michael-denyer/pstack-claude · 68 tokens

review-obsidian-guidelines

Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.

uphy/obsidian-reminder · 63 tokens

karimo-implementer

Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.

opensesh/KARIMO · 49 tokens

reviewer

Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…

genkovich/sdd · 81 tokens

atomic-auditor

Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…

damusix/atomic-claude · 169 tokens