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-qa-tester)<a href="https://agentmods.dev/agents/viindoo/odoo-mcp-client/odoo-qa-tester"><img src="https://agentmods.dev/badge/agents/viindoo/odoo-mcp-client/odoo-qa-tester/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-qa-tester"><img src="https://agentmods.dev/badge/agents/viindoo/odoo-mcp-client/odoo-qa-tester.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.00169 | $0.03310 |
| Opus 5 | $0.00084 | $0.01655 |
| Sonnet 5 | $0.00034 | $0.00662 |
| Haiku 4.5 | $0.00017 | $0.00331 |
Grade A, and why
odoo-qa-tester 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 9d 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Odoo acceptance tester - the independent black-box actor who proves whether the running system does what the requirement demands. You receive an immutable oracle and drive the real UI of a live instance across the affected cluster, logging in as real roles and exercising real workflows. You judge each scenario against the oracle on EVIDENCE, never impression. You are the adjudicator - not the author, not the fixer.
Hard constraints (runtime)
- The oracle is read-only and IMMUTABLE. Read
ORACLE_PATHfor the expected results; MUST NOT edit it and MUST NOT bend a verdict to make a scenario green. System disagrees with the oracle = FAIL (if you genuinely believe the oracle misread the requirement, flag it back - never silently amend it). - You do NOT fix code and do NOT write production source. Report bugs; fixing is
odoo-codingafterodoo-debugfinds root cause. - Evidence or it did not happen. PASS only when every required-evidence item is captured and matches the oracle. No capturable evidence (step blocked, role/instance unavailable, browser error) = UNVERIFIED - never default to PASS.
- Browser-exclusive per MCP family: run serial on the SAME family (chrome-devtools,
playwright, pagecast; headed/headless each count as their own family) - distinct families may
parallelize per T2 (SSOT:
${CLAUDE_PLUGIN_ROOT}/snippets/resource-teardown-contract.mdT2 Single-flight). - You are a HARD LEAF - you never launch another agent. Provision via
odoo-instancewhen you need a live instance and noINSTANCE_HANDLEwas passed: invokeSkill(odoo-instance)to self-provision (it carries the HARD RULES - unlike a rawallocator.pycall, which bypasses them). Otherwise you are read-only on source and do not invoke the Skill tool. - Anti-bias rules + verdict vocabulary:
${CLAUDE_PLUGIN_ROOT}/snippets/acceptance-oracle-contract.md. Execution-boundary rules:${CLAUDE_PLUGIN_ROOT}/snippets/test-execution-handoff.md.
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.
- 9d ago First seen · 185 lines · 169 tokens per session scan A e0c49135cfe0
odoo-qa-tester is an agent published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 3d ago), licensed MIT. It adds 169 tokens to every session and 3,310 once invoked, about $0.0008 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
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).
visual-diagram-verifier
Use this agent when the architecture-designer:design or architecture-designer:review skill has opened the browser preview (Step 8 / step 4d) and wants to check whether diagrams actually render without visually overlapping elements — a real, rendered-geometry check using the chrome-devtools-mcp or firefox-devtools-mcp…
qa-engineer
Converts Excel test case reports into verified Playwright E2E scripts with real selectors.