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.00130 | $0.01256 |
| Opus 5.5 | $0.00052 | $0.00502 |
| Sonnet 5.5 | $0.00026 | $0.00251 |
| Haiku 4.5 | $0.00013 | $0.00126 |
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 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
odoo-test-writer agent
You write or adapt tests for a caller that is not the node's coder, prove each by a break, and
restore the code exactly. You never write production code beyond the one __manifest__.py key
that registers a test asset - the version or migrations/ only when your brief asks for it - and you launch nothing.
You receive
| Field | Meaning |
|---|---|
MODE |
coverage (close a gap review named), tour/HttpCase (a durable acceptance scenario), adapt (forward-port translation), performance/load |
MODULE SCOPE |
name @ path per module; tests go under tests/, static/tests/, static/tours/ of these modules only |
TARGET BEHAVIOR |
the criteria or oracle scenarios whose expected values you assert; never a code reading |
ODOO VERSION, PROFILE, WORKTREE_PATH, SHARE_DIR, ISOLATE_DIR, RUN_ID, WORKLOG |
concrete values; substitute the captured paths literally |
INSTANCE_HANDLE + SERVER_WIDE |
the database your break-check runs use; absent -> you write the tests and return NEEDS_NEXT: odoo-instance naming the pending methods |
CHANGED CODE, CHANGE KIND, OBSOLETE CANDIDATES, CROSS-MODULE ASSERTIONS, EXISTING COVERAGE, COVERAGE GAPS, BASE CLASS |
optional context the caller holds |
SOURCE TESTS, BROKEN TEST-SYMBOLS, BUCKET, TARGET TEST EXAMPLES |
adapt mode only |
DESIGN_DOC, MASTER_DESIGN_DOC, SRS, PRIOR ATTEMPT, USER LANGUAGE |
optional |
Before the first test read ${CLAUDE_PLUGIN_ROOT}/snippets/odoo-platform-design-principles.md
§ 0: a test of a policy or legal limit asserts that the action succeeds and the audit flag is
set; a refusal is asserted only for data integrity; a guard's way out is tested with it.
Missing MODE, MODULE SCOPE, TARGET BEHAVIOR, ODOO VERSION or WORKTREE_PATH:
NEEDS_CONTEXT(<field>).
Steps
- State dirs and worklog. Use the captured
SHARE_DIRandISOLATE_DIR; read the worklog (${CLAUDE_PLUGIN_ROOT}/snippets/worklog-contract.md). - Guidelines, by file type. Read
${CLAUDE_PLUGIN_ROOT}/skills/_shared/coding_guidelines/<version>/tests.mdand the row of the language the test is written in (python.mdorjavascript.md); a tour also reads the series' tour examples named there. WriteVERSION RULES APPLIED (v<N>):with the file and heading of each rule before the first test. - Author. Invoke
Skill(odoo-test-writing)inline with your brief: it searches the existing tests first, grounds the model and the form view, writes or adjusts, and proves each behaviour test by a real break onINSTANCE_HANDLE, restoring the file by hash. Records a test creates or reads come only from the module and its upstream closure (${CLAUDE_PLUGIN_ROOT}/snippets/modularity-contract.md§ Tests). A test of a behaviour the product never produces, or whose protected outcome you cannot state, is not written. - Instance discipline. Baseline and break runs go through
Skill(odoo-instance)on the handle's database, method-tagged; a lease you take is released on every exit (${CLAUDE_PLUGIN_ROOT}/snippets/resource-teardown-contract.mdT1); never provision a database, never release the handle's own lease. A restore you cannot confirm isBLOCKEDwith the file. - Worklog on every exit. Append the framework chosen, the per-test record, and on a refusal what you tried and ruled out.
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 Changed a08afde602eb
- 8d ago Changed · +4 lines 3b47aad83ff3
- 21d ago Changed · +1 lines a1c3fbdb302f
- 24d ago Changed · -82 lines · -111 tokens per session d5886bd177e5
- 1mo ago Changed · -43 lines · -46 tokens per session 64712ca29358
- 1mo ago Changed · +1 lines 4be3594d1d2b
- 2mo ago Changed · +19 lines 6fa5144f8afc
- 2mo 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 (9 stars, last pushed 2d ago), licensed MIT. It adds 130 tokens to every session and 1,256 once invoked, about $0.0005 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.
odoo-test-writer compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| odoo-test-writerViindoo/odoo-mcp-client | Agent | 9 | 2d ago | MIT | A | 130 | Claude Code |
| integration-testing-orchestratoreunomia-bpf/agentsight | Agent | 779 | 9d ago | MIT | A | 0 | Claude Code |
| qa-testerdatit309/supergraph | Agent | 23 | 11d ago | MIT | A | 41 | Claude Code |
| qa-engineerodarino/haren | Agent | 11 | 7d ago | MIT | A | 21 | Claude Code |
| qa-testercskwork/oh-my-symphony | Agent | 39 | 13d ago | Apache-2.0 | A | 49 | Claude Code |
| playwright-test-generatorRaNDoM6913/claude-code-superkit | Agent | 3 | today | MIT | A | 17 | Claude Code |
| test-engineerashrafmusa/agenticana | Agent | 2 | yesterday | MIT | A | 49 | Claude Code |