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/skills/viindoo/odoo-mcp-client/odoo-acceptance)<a href="https://agentmods.dev/skills/viindoo/odoo-mcp-client/odoo-acceptance"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-acceptance/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/skills/viindoo/odoo-mcp-client/odoo-acceptance"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-acceptance.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.00255 | $0.04726 |
| Opus 5 | $0.00128 | $0.02363 |
| Sonnet 5 | $0.00051 | $0.00945 |
| Haiku 4.5 | $0.00026 | $0.00473 |
Grade C, and why
odoo-acceptance scanned grade C with 1 finding 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 10d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
`find <ISOLATE_DIR>/visual/qa/ -mindepth 1 -maxdepth 1 -type d -mmin +43200 -exec rm -rf {} +` How it starts
The opening of the file, as written. The whole thing — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Odoo acceptance conductor: own the loop that closes a change - map blast-radius -> plan an
independent oracle -> execute it live across the affected cluster -> adjudicate against the oracle ->
drive the fix. Keep your context clean; delegate each heavy phase to a specialist. Preserve the
anti-bias invariant: oracle author, code author, and adjudicator are three different contexts
(${CLAUDE_PLUGIN_ROOT}/snippets/acceptance-oracle-contract.md). EXECUTION needs a live Odoo instance
(via odoo-instance) plus a browser MCP; Odoo Semantic is STATIC and never a source of live data.
Sole dispatcher of acceptance fan-out. This skill is the ONLY component that launches the
odoo-qa-planner (independent oracle author) and odoo-qa-tester (live executor + adjudicator)
agents. Any other skill needing an oracle authored and/or executed-and-adjudicated routes that work
HERE via the Skill tool - centralizing the three-context invariant and the per-family browser
exclusivity rule. Provision live execution by invoking the odoo-instance skill.
Dispatch-brief skeleton. When composing the dispatch prompt for odoo-qa-planner,
odoo-qa-tester, or any other specialist agent dispatched below, fill the caller-side skeleton in
${CLAUDE_PLUGIN_ROOT}/snippets/dispatch-brief.md (read it by path) plus the target agent's family
delta; never inline that file verbatim into a hard-leaf brief.
Out of Scope
- A static release test-plan doc, deploy checklist, or user-level bug triage (no execution) ->
odoo-qa-suite - Rating ONE rendered screen (aesthetics/a11y/perf/theme verdict, read-only) ->
odoo-ui-review - Static review of a diff / PR / pasted block (no run) ->
odoo-code-review - Writing or fixing the code ->
odoo-coding; finding root cause of one symptom ->odoo-debug - Writing a standalone durable test (a tour/HttpCase with no live acceptance loop) ->
odoo-test-writing - Authoring the oracle alone (no execution wanted) -> still THIS skill (run Phase 1 only) - it is the sole dispatcher of
odoo-qa-planner; do NOT spawn the raw agent - Writing walkthrough TEXT or usage scenarios for documentation (no execution required) ->
odoo-doc-walkthrough. This skill drives live UI and yields a PASS/FAIL verdict; it does NOT produce text-only scenario docs
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 249 lines · 255 tokens per session scan C b474ef570c29
odoo-acceptance is a skill published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 3d ago), licensed MIT. It adds 255 tokens to every session and 4,726 once invoked, about $0.0013 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…