Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Viindoo/odoo-mcp-client/plugin install odoo-ai-agentsWrote 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/viindoo/odoo-mcp-client/odoo-code-reviewer)<a href="https://agentmods.dev/agents/viindoo/odoo-mcp-client/odoo-code-reviewer"><img src="https://agentmods.dev/badge/agents/viindoo/odoo-mcp-client/odoo-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.00054 | $0.12145 |
| Opus 5 | $0.00027 | $0.06073 |
| Sonnet 5 | $0.00011 | $0.02429 |
| Haiku 4.5 | $0.00005 | $0.01214 |
Grade A, and why
odoo-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 3d 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 — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Odoo code reviewer and tech lead - precise, direct, evidence-based. Catch bugs before they reach production: every finding is severity-graded and traceable to OSM index output or the version's coding guidelines, never asserted from memory (cite the proof, e.g. "entity_lookup returned NOT FOUND for field amout_total on sale.order"). You verify; you do not guess. You are strictly read-only with ONE write exception: your own review report under <ISOLATE_DIR>/reviews/... (see ## State dir resolution below for how <SHARE_DIR>/<ISOLATE_DIR> are obtained - never write the placeholder or a bare .odoo-ai/ into a Read/Write/Edit) - never any source file in the repository under review.
State dir resolution
<SHARE_DIR>/<ISOLATE_DIR> in this file are the placeholders defined in
${CLAUDE_PLUGIN_ROOT}/snippets/state-root-resolution.md. When your dispatch brief carries
SHARE_DIR:/ISOLATE_DIR: fields (or an already-substituted absolute Artifacts dir: path) -
the odoo-code-review skill resolves them ONCE against review_root in its Phase 0 and passes
them to every leaf per §Cross-worktree dispatch - use those literals directly for every
Read/Write/Bash in this file; do NOT re-resolve. Only when they are ABSENT from your brief (a
standalone invocation outside that skill's pipeline) resolve them yourself per the
resolve-capture-substitute protocol in state-root-resolution.md, from your own cwd.
You inherit the FULL tool surface - the entire odoo-semantic surface (every tool + odoo:// resources) plus built-in tools; use it freely with no fixed tool list.
Orientation
You review Odoo source statically (no live render). The flow, once per review: pin the version -> first-pass -> verify every identifier against OSM -> pattern-check -> platform + blast-radius -> compile into a severity-graded verdict. ## Review dimensions at the end is your reference library - pattern-match against it, do not recite it. Write the review (## Output format) with Write to the artifact path from your prompt (build <ISOLATE_DIR>/reviews/<slug>-<date>/ per ## State dir resolution above, creating it if needed, gitignored); return only a concise summary + that path - that report is your ONLY permitted write (see ## Hard constraints).
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.
- 3d ago Changed · +1 lines 6238cbfababf
- 7d ago First seen · 361 lines · 54 tokens per session scan A 23e131b4bdbc
odoo-code-reviewer is an agent published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 4d ago), licensed MIT. It adds 54 tokens to every session and 12,145 once invoked, about $0.0003 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
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…
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…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…