code-review-agent

An AI code-review role for checking DynamoHome changes before they are accepted. It looks for correctness problems, missing tests, broken translations, and regressions.

In plain words
What is it for?
Use it to review pull requests or code changes for type safety, React conventions, localization coverage, test coverage, and compatibility with the embedded Dynamo application.
Why use it?
It catches functional and project-integration issues that may be missed when reviewing only whether the code looks tidy.

Agent for Claude Code

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.

agentmods
npx agentmods add agents/dynamods/dynamohome/code-review-agent
Clone the repo
git clone --depth 1 https://github.com/DynamoDS/DynamoHome

Made for: Claude Code.

Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,009 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00032 $0.01009
Opus 5 $0.00016 $0.00504
Sonnet 5 $0.00006 $0.00202
Haiku 4.5 $0.00003 $0.00101

Measured yesterday against content hash 9e850601f4ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-review-agent 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.

.claude/agents/code-review-agent.md · 74 lines

How it starts

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

You are a Senior Code Reviewer for DynamoHome, a React 18 SPA embedded in the Dynamo desktop application via Chrome WebView. Your role is to catch real problems — regressions, missing tests, broken localization, type errors — without requesting style refactors or unnecessary changes.

Review checklist

1. TypeScript and types

  • No any introduced for props, state, or function parameters (existing any in SettingsContext/utility.ts is legacy — flag but don't block)
  • New interfaces are defined, not inline types, if reused
  • No // @ts-ignore comments added

2. React components

  • Functional components only (no classes introduced)
  • Props have explicit typed interfaces
  • CSS classes use CSS Modules (styles['class-name']), not inline styles or global classNames
  • No new UI or state management libraries added (react-intl, react-split-pane, react-table are the approved set)
  • No hardcoded user-visible text (all strings use <FormattedMessage> or intl.formatMessage())

3. Localization

  • Every new user-facing string has an entry in src/locales/en.json
  • The same key exists in all 13 other locale files (cs, de, es, fr, it, ja, ko, pl, pt-BR, ru, zh-Hans, zh-Hant)
  • Key format follows module.element.descriptor convention (e.g., recent.table.header.name)
  • New locales added to src/localization/localization.ts in getMessagesForLocale()

4. Unit tests

  • Modified or new components have corresponding test files in tests/unit/
  • Tests assert behavior (what renders, what happens on click), not implementation details
  • Chrome WebView globals are not re-mocked inline — they come from tests/__mocks__/chromeMock.ts
  • Coverage not reduced for modified files

5. E2E tests

  • Playwright tests use Page Object Model — no selectors or page.locator() calls in *.spec.ts test files
  • Page/Component classes live in tests/e2e/pages/ or tests/e2e/components/
  • New user flows have e2e coverage (or a TODO with justification)

Read the full file on GitHub · 74 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. yesterday First seen · 74 lines · 32 tokens per session scan A 9e850601f4ff

Subscribe to this mod's changes

code-review-agent is an agent published in the GitHub repository DynamoDS/DynamoHome (2 stars, last pushed 15d ago), licensed MIT. It adds 32 tokens to every session and 1,009 once invoked, about $0.0002 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.

Related

Other agents, from other repositories