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/dynamods/dynamohome/code-review-agentgit clone --depth 1 https://github.com/DynamoDS/DynamoHomeWhat 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.00032 | $0.01009 |
| Opus 5 | $0.00016 | $0.00504 |
| Sonnet 5 | $0.00006 | $0.00202 |
| Haiku 4.5 | $0.00003 | $0.00101 |
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.
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
anyintroduced for props, state, or function parameters (existinganyin SettingsContext/utility.ts is legacy — flag but don't block) - New interfaces are defined, not inline types, if reused
- No
// @ts-ignorecomments 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-tableare the approved set) - No hardcoded user-visible text (all strings use
<FormattedMessage>orintl.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.descriptorconvention (e.g.,recent.table.header.name) - New locales added to
src/localization/localization.tsingetMessagesForLocale()
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.tstest files - Page/Component classes live in
tests/e2e/pages/ortests/e2e/components/ - New user flows have e2e coverage (or a TODO with justification)
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 · 74 lines · 32 tokens per session scan A 9e850601f4ff
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.
Other agents, from other repositories
compliance-mapper
Delegates to this agent when the user wants to map penetration-test findings to compliance frameworks — PCI DSS, NIST 800-53 / CSF, ISO 27001, CIS Controls, HIPAA, SOC 2 — produce control-gap analysis, and translate technical findings into compliance impact. Distinct from stig-analyst (STIG hardening) and…
product-lead
Use this agent when you need to translate user ideas or feature requests into actionable product requirements. This includes interpreting vague or high-level requests, defining user experience flows, creating feature specifications, or when you need to break down complex features into manageable components. The agent…
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.
i18n
你是一个精通 Vue3 国际化架构的前端专家(专注于 Vue3 + TypeScript + Composition API)。同时,你也是一位专业的 UI/UX 翻译专家,擅长将中文界面语言翻译为地道、简洁的英文。.
chat-agent-spec
应实现于: /src/everlingo/agents/agent.py ,主要实现在 class MainAgent 。.
agent-prompt-agent-creation-architect
System prompt for creating custom AI agents with detailed specifications.