agentmods.dev

odoo-ui-debugger

odoo-ui-debugger is an agent for Claude Code from Viindoo/odoo-mcp-client. It costs 152 tokens per session (6,583 once invoked), scanned A, original, MIT.

A specialist agent for finding the proven cause of problems in a live Odoo web interface. OWL is Odoo's JavaScript interface framework, while RPC is how the interface calls the server.

In plain words
What is it for?
Use it to investigate blank screens, missing widgets, failed server calls, broken style overrides, incorrect themes, or JavaScript errors after an upgrade. It reports where the fix belongs but does not edit the source.
Why use it?
It connects browser evidence—such as errors, requests, page structure, and styles—with the Odoo code that produced it. This helps distinguish the actual cause from guesses.

Agent for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: model in frontmatter; $skill-name invocation.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the odoo-ai-agents plugin — 50 skills, 8 commands, 23 agents, 8 hooks, 3 MCP servers shipped together

not rated 9repo changed 19d ago A scan 152 tokens original MIT

Good fit Use it to investigate blank screens, missing widgets, failed server calls, broken style overrides, incorrect themes, or JavaScript errors after an upgrade. It reports where the fix belongs but does not edit the source.

Compare 6 agents from other repositories ↓
View source ↗ Viindoo/odoo-mcp-client odoo-semantic.viindoo.com
Install

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.

Claude Code
/plugin marketplace add Viindoo/odoo-mcp-client
Claude Code
/plugin install odoo-ai-agents

Made for: Claude Code.

Or install odoo-ai-agents, the plugin that ships this one along with the rest of its 50 skills, 8 commands, 23 agents, 8 hooks, 3 MCP servers.

Wrote 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.

agentmods badge for odoo-ui-debugger

README.md
[![agentmods](https://agentmods.dev/badge/agents/viindoo/odoo-mcp-client/odoo-ui-debugger/github.svg)](https://agentmods.dev/agents/viindoo/odoo-mcp-client/odoo-ui-debugger)
Your own site
<a href="https://agentmods.dev/agents/viindoo/odoo-mcp-client/odoo-ui-debugger"><img src="https://agentmods.dev/badge/agents/viindoo/odoo-mcp-client/odoo-ui-debugger/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.

agentmods 80×15 button for odoo-ui-debugger

Your own site · 80×15
<a href="https://agentmods.dev/agents/viindoo/odoo-mcp-client/odoo-ui-debugger"><img src="https://agentmods.dev/badge/agents/viindoo/odoo-mcp-client/odoo-ui-debugger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 152 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 6,583 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00152 $0.06583
Opus 5.5 $0.00061 $0.02633
Sonnet 5.5 $0.00030 $0.01317
Haiku 4.5 $0.00015 $0.00658

Measured 19d ago against content hash 9a883666a832, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

odoo-ui-debugger 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 19d 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.

plugins/odoo-ai-agents/agents/odoo-ui-debugger.md · 350 lines

How it starts

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

You are a senior Odoo runtime frontend debugger with deep expertise in OWL 2 components, QWeb templates, SCSS/CSS token cascades, Odoo asset bundles, and browser devtools. Mission: take a symptom in the live UI back to a single PROVEN root cause by DUAL-SOURCING evidence - correlating live browser signals (console, network, DOM snapshot, computed styles) with the indexed codebase (stylesheet origin, override chain, JS examples, API diffs) - and name the exact file, method, or selector to change, never a guess. BROWSER-EXCLUSIVE agent: you drive a real browser and MUST run as the only browser-driving agent on your MCP family at a time (distinct families may run in parallel). Root-cause-first rule: no fix is proposed before the root cause is proven. Read-only - you hand the fix to a coding agent.

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: you do NOT edit any source file or modify the running Odoo instance (you still append your own worklog under the $ODOO_AI_HOME state root, see ${CLAUDE_PLUGIN_ROOT}/snippets/state-root-resolution.md). This agent diagnoses and names the fix location only - it does not write the fix. 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 - on a headless host the headed server fails to launch. Pick one variant for the whole diagnosis and stay on it.

Report language

If the dispatch brief sets USER LANGUAGE: <language>, write human-facing prose (the summary field, user-facing text) in it; all code, comments, docstrings, identifiers, file paths, commit messages, and tool names stay English. Without it, report in English and the orchestrator translates when relaying (SSOT: ${CLAUDE_PLUGIN_ROOT}/snippets/language-mirroring.md).

Read the full file on GitHub · 350 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. 19d ago Changed · -10 lines 9a883666a832
  2. 24d ago Changed · +14 lines f1d095b79bed
  3. 1mo ago Changed a4be97eac9b7
  4. 1mo ago Changed 1404d0759d5a
  5. 1mo ago Changed · -5 lines 0e045ad8d1e6
  6. 1mo ago Changed 78c8cad00444
  7. 1mo ago Changed 39ebf1352e1e
  8. 2mo ago Changed · +5 tokens per session bcc212edee18
  9. 2mo ago First seen · 351 lines · 147 tokens per session scan A e5f334745521

Subscribe to this mod's changes

odoo-ui-debugger is an agent published in the GitHub repository Viindoo/odoo-mcp-client (9 stars, last pushed 2d ago), licensed MIT. It adds 152 tokens to every session and 6,583 once invoked, about $0.0006 per session on Opus 5.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.

DebuggingFrontend
Related

odoo-ui-debugger compared with agents from other repositories

odoo-ui-debugger next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
odoo-ui-debuggerViindoo/odoo-mcp-clientAgent92d agoMITA152Claude Code
review-obsidian-guidelinesuphy/obsidian-reminderAgent6625d agoMITA63Claude Code
debuggerTT-Wang/forgeAgent356d agoMITA17Claude Code
loom-advisorcosmix/loomAgent66todayMITA53Claude Code
debuggerbostonaholic/rpikitAgent19yesterdayMITA28Claude Code
evolve-retrospectivemickeyyaya/evolve-loopAgent7todayApache-2.0A51Claude Code
type-reconstructormarcosd4h/DeepExtractRuntimeAgent211mo agoMITA63Claude Code