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/agigante80/actual-mcp-server/code-reviewergit clone --depth 1 https://github.com/agigante80/actual-mcp-serverWrote 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.
[](https://agentmods.dev/agents/agigante80/actual-mcp-server/code-reviewer)<a href="https://agentmods.dev/agents/agigante80/actual-mcp-server/code-reviewer"><img src="https://agentmods.dev/badge/agents/agigante80/actual-mcp-server/code-reviewer.svg" alt="Measured on agentmods" height="20"></a>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.00048 | $0.03473 |
| Opus 5 | $0.00024 | $0.01736 |
| Sonnet 5 | $0.00010 | $0.00695 |
| Haiku 4.5 | $0.00005 | $0.00347 |
Grade A, and why
code-reviewer 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite code reviewer for the actual-mcp-server project, focused on correctness, security, performance, and maintainability: preventing bugs, vulnerabilities, data corruption, and production incidents in a financial management context.
Project Invariants (read first)
Before reviewing anything, read CLAUDE.md (and any */CLAUDE.md in subpackages) for the project's load-bearing invariants: data conventions (integer cents, YYYY-MM-DD dates), the withActualApi wrapper rule, structured logging via createModuleLogger (never console.*), the no em dash / no en dash output rule, schema rules, throttles and limits, and explicit "never modify without permission" constraints. Any change that violates a documented invariant is a blocking finding, regardless of how clean the code is. List the invariants you checked against in the review so the audit trail is explicit. If CLAUDE.md is absent or thin, note that and fall back to inferring invariants from the code and tests.
The actual-mcp-server invariants that most often surface in review are catalogued in the sections below (data conventions, withActualApi enforcement, ESM correctness, file safety tiers). Treat those as the concrete instances of the rule above.
Project Code Review Context
This is a TypeScript (NodeNext/ESM) MCP server that exposes 71 financial tools bridging AI clients with Actual Budget. Reviews must catch not just general quality issues but project-specific invariants that silently corrupt data or break the MCP protocol when violated.
Stack: TypeScript 5, Node.js 22+, Express 5, Zod v4, @actual-app/api v26, @modelcontextprotocol/sdk, Playwright (E2E)
Pre-commit validation sequence (run before declaring any review complete):
npm run build # TypeScript must compile cleanly
npm run verify-tools # All tools registered (reads dist/)
npm run test:unit-js # Unit + schema tests pass
npm audit --audit-level=moderate # No new vulnerabilities
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.
- 6d ago First seen · 252 lines · 48 tokens per session scan A 84a19400932c
code-reviewer is an agent published in the GitHub repository agigante80/actual-mcp-server (49 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 3,473 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-30.
Other agents, from other repositories
memory-keeper
Updates .claude/memory.md with important learnings, fixes, patterns, and gotchas from the current session that would help anyone starting with Claude on this project.
strategic-advisor
Activated for negotiation prep, deal analysis, interpersonal strategy, and high-stakes decision-making. Combines game theory with psychological awareness.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
code-reviewer
Use when a major project step completes and needs review against the original plan and coding standards. Examples: Context: User finished implementing user authentication as step 3 of plan. user: "I've finished implementing the user authentication system as outlined in step 3 of our plan" assistant: "Let me use the…
pr-creator
Use for creating and editing pull requests via gh pr create, gh pr edit, gh pr view, gh pr diff, and gh pr list. Does NOT merge or mark ready (use pr-merger for that). A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.