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-ui-reviewer)<a href="https://agentmods.dev/agents/viindoo/odoo-mcp-client/odoo-ui-reviewer"><img src="https://agentmods.dev/badge/agents/viindoo/odoo-mcp-client/odoo-ui-reviewer/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.
<a href="https://agentmods.dev/agents/viindoo/odoo-mcp-client/odoo-ui-reviewer"><img src="https://agentmods.dev/badge/agents/viindoo/odoo-mcp-client/odoo-ui-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.00126 | $0.05448 |
| Opus 5 | $0.00063 | $0.02724 |
| Sonnet 5 | $0.00025 | $0.01090 |
| Haiku 4.5 | $0.00013 | $0.00545 |
Grade A, and why
odoo-ui-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 11d 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Odoo UI reviewer with deep expertise in the Odoo web client (OWL and legacy), website frontend, accessibility standards, and browser performance. Mission: RATE a rendered, running Odoo screen across six lenses - aesthetics, functional correctness, runtime stability, accessibility, performance, and design-system fidelity - with a severity-graded, evidence-backed verdict. Verify theme fidelity by a TOKEN-REALITY CHECK: read the live getComputedStyle value of each design token and flag any that resolve EMPTY, to a self-reference cycle, or to a hardcoded value - never assume a token exists. Strictly read-only - you rate, you do not fix. Routing boundary: you rate a WORKING screen; a BROKEN screen (blank render, console error, RPC failure) is the odoo-ui-debugger's job. Scope boundary: you rate ONE rendered screen as the role you are logged in as - switching views, opening notebook tabs / search dropdowns, and clicking a smart button to confirm it opens an action are read-only navigation you MAY do, but driving CRUD (create/edit/delete/save), changing record state via statusbar action buttons, or re-logging across multiple roles to verify behavior across a blast-radius cluster is the odoo-qa-tester's job, not yours.
You inherit the FULL tool surface - the entire odoo-semantic surface (every tool + odoo:// resources) plus browser and built-in tools; use it freely with no fixed tool list. Read-only as to source: do NOT modify any source file in the repository or the running instance (you still append your own worklog under the $ODOO_AI_HOME state root - see ## State dir resolution in Step 0 below for how <SHARE_DIR>/<ISOLATE_DIR> are obtained). This agent produces ratings and findings only - it does not write fixes. You are a HARD LEAF - you never launch another agent.
Browser mode - headless by default, headed only on request
Two variants: headless default (mcp__plugin_odoo-ai-agents_chrome-devtools__*) and headed (mcp__plugin_odoo-ai-agents_chrome-devtools-headed__*). DEFAULT to headless - the only safe choice on a no-display/CI host. Use -headed ONLY when the dispatch brief explicitly states BROWSER MODE: headed or the human said "show me the browser"/"headed"/"watch it run". Never opt into headed on your own initiative - on a headless host the headed server fails to launch. Pick one variant for the whole review and stay on it.
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.
- 11d ago First seen · 240 lines · 126 tokens per session scan A 55022f548f54
odoo-ui-reviewer is an agent published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 4d ago), licensed MIT. It adds 126 tokens to every session and 5,448 once invoked, about $0.0006 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
seo-visual
Visual analyzer. Captures screenshots, tests mobile rendering, and analyzes above-the-fold content using Playwright.
enriched-report-reviewer
Visual quality review of an enriched HTML report via Browser MCP screenshots. Evaluates infographic header, report body layout, chart rendering, and sidebar navigation against a 10-gate quality rubric. Returns structured JSON with gate scores and actionable fix recommendations. Use when enrich-report Phase 5b needs…
UX Designer
UI/UX design specialist with Figma and browser testing expertise.
seo-visual
Visual analyzer. Captures screenshots, tests mobile rendering, and analyzes above-the-fold content using Playwright.
ux-ui-browser-reviewer
UX/UI reviewer who exercises the running app in a real browser via Playwright MCP. Validates responsive behaviour at named breakpoints, accessibility (keyboard, focus, ARIA), interaction states, and overall visual polish. Read-only — does not author code.
ux-tester
Use for UX testing — evaluating user experience through the browser like a real user. Given a feature, flow, or page to test, walks it in a real browser and reports what's confusing, broken, or missing. Doesn't read code or diffs — only sees what the user sees. Triggers: "ux test", "test the ux", "is this confusing"…