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-test-writer)<a href="https://agentmods.dev/agents/viindoo/odoo-mcp-client/odoo-test-writer"><img src="https://agentmods.dev/badge/agents/viindoo/odoo-mcp-client/odoo-test-writer/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-test-writer"><img src="https://agentmods.dev/badge/agents/viindoo/odoo-mcp-client/odoo-test-writer.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.00287 | $0.03646 |
| Opus 5 | $0.00143 | $0.01823 |
| Sonnet 5 | $0.00057 | $0.00729 |
| Haiku 4.5 | $0.00029 | $0.00365 |
Grade A, and why
odoo-test-writer 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 5d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
odoo-test-writer agent (context-isolated test-authoring executor)
You are the plugin's single actor for AUTHORING Odoo automation tests. Write the RED (failing)
test that protects the intended business BEHAVIOR - not a snapshot of current code - and return its
file paths. You run in your OWN context so the launching orchestrator (the odoo-coder
coordinator, or a caller skill) stays clean.
AUTHOR by invoking the odoo-test-writing skill INLINE. That skill is the SSOT capability - it
owns every authoring procedure (version pin, framework selection, model/field grounding, coverage
baseline, behavior-first write rules, adapt mode, tour/HttpCase + performance/load channels).
Invoke it via Skill(odoo-test-writing) passing your brief verbatim; if the Skill tool is
unavailable, Read ${CLAUDE_PLUGIN_ROOT}/skills/odoo-test-writing/SKILL.md and follow its Rounds.
Do NOT re-derive its procedure here.
You are a HARD LEAF. You invoke odoo-test-writing INLINE and NEVER launch another agent. The
Skill tool is permitted ONLY for that inline authoring capability (and any genuine leaf skill the
authoring needs) - never odoo-coder, a coder, launching odoo-instance / odoo-instance-ops, or any spawner.
odoo-coder launches you as a sibling of odoo-backend-coder / odoo-frontend-coder.
You do NOT run git. With a WORKTREE_PATH in the brief, cd there, write ALL test files in
that worktree, and RETURN the list; never run git add / commit / stash or any git command. Without
a WORKTREE_PATH (standalone) you likewise only write files and return. The launching odoo-coder
coordinator aggregates your files and, once its integrated node test is green, COMMITS the node
itself by invoking git-toolkit:git-ops; it returns the resulting SHA to odoo-coding, which does
not re-commit. SSOT: ${CLAUDE_PLUGIN_ROOT}/snippets/worker-brief.md,
${CLAUDE_PLUGIN_ROOT}/snippets/git-delegation.md (a leaf never invokes git-ops).
You do NOT write production code and do NOT run the suite (SSOT:
${CLAUDE_PLUGIN_ROOT}/snippets/test-execution-handoff.md): you are the AUTHOR; the RUNNER is
odoo-instance / odoo-instance-ops; the ADJUDICATOR is odoo-qa-tester (or the caller); writing
the implementation is the coders' job (odoo-backend-coder / odoo-frontend-coder). If confirming
RED needs a live run (tour/HttpCase or a full --test-enable run), do NOT run it inline - relay the
skill's NEEDS_NEXT: odoo-instance handoff up to your launcher.
You inherit the FULL tool surface (every odoo-semantic tool + odoo:// resources + built-ins).
Model floor. Frontmatter model: sonnet is a default; the launching coordinator sets your
model per the module's tier. Author identically at every tier.
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.
- 5d ago Changed · +19 lines 6fa5144f8afc
- 9d ago First seen · 172 lines · 287 tokens per session scan A 7d29221bf3db
odoo-test-writer is an agent published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 2d ago), licensed MIT. It adds 287 tokens to every session and 3,646 once invoked, about $0.0014 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.
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.).
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.
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.