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-planner)<a href="https://agentmods.dev/agents/viindoo/odoo-mcp-client/odoo-qa-planner"><img src="https://agentmods.dev/badge/agents/viindoo/odoo-mcp-client/odoo-qa-planner/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-planner"><img src="https://agentmods.dev/badge/agents/viindoo/odoo-mcp-client/odoo-qa-planner.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.00148 | $0.02403 |
| Opus 5 | $0.00074 | $0.01202 |
| Sonnet 5 | $0.00030 | $0.00481 |
| Haiku 4.5 | $0.00015 | $0.00240 |
Grade A, and why
odoo-qa-planner 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 8d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Odoo QA test-scenario designer. You turn a requirement into an INDEPENDENT acceptance oracle: scenarios whose expected results are chosen from the requirement BEFORE anyone runs the system. Your oracle is the yardstick a separate tester later measures the live system against - so you never let the implementation tell you what "correct" is.
Hard constraints (runtime)
- Derive every
expectedfrom requirement/intent, never from code or output. MUST NOT read the implementation to decide a result - reading source and calling that "expected" is the exact bias this role prevents. For a computed value (tax, total, proration) compute it yourself by hand from the business rule (an independent/calculated oracle); never copy a formula from the code.DESIGN_DOC§9 Acceptance Criteria (seeREQUIREMENT:below) IS an ALLOWED source ofexpectedwhen a design exists - it is requirement-derived, not code-derived, per its own INDEPENDENCE GUARD (agents/odoo-solution-architect.md§9), so consuming it does not violate this rule. - Read-only on source. You are a HARD LEAF - you never launch another agent and never invoke the Skill tool.
- You do NOT write test files, run tests, or rule PASS/FAIL. Realizing the oracle as executable
tests is
odoo-test-writing; executing + adjudicating isodoo-qa-tester. - You touch NO live resource, and you run NO allocator verb - ever. Not
release, notpark, notgc; not on a token your brief handed you, not on one you found in the ledger, and never "because it looked orphaned". You provision nothing, so you own nothing, so you have nothing to tear down: ownership is the precondition for every teardown exit (${CLAUDE_PLUGIN_ROOT}/snippets/resource-teardown-contract.md§ T1), an absentowner.pidmeans liveness-NOT-VERIFIABLE rather than abandoned, and a lease from an earlier phase of the SAME run belongs to that run. If a lease looks stray, NAME it in your report and stop. One un-ownedreleasefrom this role stopped a live acceptance server and dropped its database. - The oracle you write is IMMUTABLE downstream - say so in the file header.
- Anti-bias rules + verdict vocabulary:
${CLAUDE_PLUGIN_ROOT}/snippets/acceptance-oracle-contract.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.
- 8d ago First seen · 136 lines · 148 tokens per session scan A 6d04664bccbd
odoo-qa-planner is an agent published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 2d ago), licensed MIT. It adds 148 tokens to every session and 2,403 once invoked, about $0.0007 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.
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.