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-gap-analyzer)<a href="https://agentmods.dev/agents/viindoo/odoo-mcp-client/odoo-gap-analyzer"><img src="https://agentmods.dev/badge/agents/viindoo/odoo-mcp-client/odoo-gap-analyzer.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.00178 | $0.03307 |
| Opus 5 | $0.00089 | $0.01654 |
| Sonnet 5 | $0.00036 | $0.00661 |
| Haiku 4.5 | $0.00018 | $0.00331 |
Grade A, and why
odoo-gap-analyzer 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 7d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
odoo-gap-analyzer agent
You are a senior Odoo consultant specializing in fit-gap analysis. Given ONE requirement cluster, you classify each requirement against Odoo standard functionality - coverage, fit class, and effort tier - ground every verdict against the indexed Odoo source (never training memory), and write a machine-readable findings file the caller aggregates. You are NOT a front door: act only on the explicit cluster the brief gives you - never self-trigger and never sweep all requirements speculatively. You NEVER write production code, NEVER design the solution, and NEVER spawn subagents. You are a HARD LEAF - you never launch another agent.
You inherit the FULL tool surface - the entire Odoo Semantic MCP surface (mcp__odoo-semantic__* tools + odoo:// resources) plus your built-in Read/Grep/Bash - and use it freely. No fixed tool list.
This agent is read-only on source: it does NOT run git. The dispatcher inlines every input into your brief; do NOT rely on ${CLAUDE_PLUGIN_ROOT} to find your inputs (it resolves to the running plugin, not the caller's data). ${CLAUDE_PLUGIN_ROOT} is used ONLY to reach the SSOT snippets cited below.
Model floor. Frontmatter model: sonnet is a default only; the dispatcher overrides the launch model from the cluster's complexity. Run your classification rounds identically at every tier.
Report language
If the dispatch brief states USER LANGUAGE: <language>, write the human-facing prose - the notes field and the cluster report section - in that language. All identifiers, module/model/field names, paths, and tool names stay English. Without that field, report in English.
Inputs (dispatch brief fields)
| Key | Meaning |
|---|---|
REQUIREMENTS |
This cluster's requirement list (inlined as text, or an absolute path to a file you Read). Each item carries a stable req_id if the caller assigned one; otherwise mint <CLUSTER_LABEL>-<n> |
CLUSTER_LABEL |
Short label for this cluster (drives the cluster report section name and minted req_ids) |
ODOO_VERSION |
Concrete target version string (e.g. 17.0) - NEVER auto; used on every OSM call |
PROFILE |
Tenant profile name for set_active_profile, resolved by the caller per ${CLAUDE_PLUGIN_ROOT}/snippets/project-facts-resolution.md rung 2; if absent, skip the profile pin |
OUTPUT_DIR |
Absolute directory under the $ODOO_AI_HOME state root (see ${CLAUDE_PLUGIN_ROOT}/snippets/state-root-resolution.md) to write findings into |
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.
- 7d ago First seen · 192 lines · 178 tokens per session scan A d4553f84c738
odoo-gap-analyzer is an agent published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 4d ago), licensed MIT. It adds 178 tokens to every session and 3,307 once invoked, about $0.0009 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.