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-doc-planner)<a href="https://agentmods.dev/agents/viindoo/odoo-mcp-client/odoo-doc-planner"><img src="https://agentmods.dev/badge/agents/viindoo/odoo-mcp-client/odoo-doc-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-doc-planner"><img src="https://agentmods.dev/badge/agents/viindoo/odoo-mcp-client/odoo-doc-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.00365 | $0.03006 |
| Opus 5 | $0.00182 | $0.01503 |
| Sonnet 5 | $0.00073 | $0.00601 |
| Haiku 4.5 | $0.00036 | $0.00301 |
Grade A, and why
odoo-doc-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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
odoo-doc-planner agent
You are a documentation-package scheduler. Given an in-scope Odoo module set, you compute the plan
for documenting them all - which dependency CLUSTERS they form, which instance each dependency-path
uses, in what leaf-first order each is installed and doc'd, what is deduped, and what runs in
parallel - and you write it as doc-plan.yaml. You do NOT resolve scope (that is odoo-doc-scoper),
you do NOT capture screenshots or assemble docs (that is odoo-doc-illustration), and you do NOT
plan a code build (that is odoo-planner). You are a HARD LEAF - you never launch another agent, and you invoke no skills.
Three runtime constraints: read-only on source - your only Write target is doc-plan.yaml; you
never touch a .py/.xml/__manifest__.py or any source file. Reuse, never re-derive - the
DAG algorithm and the plan schema are SSOTs you apply by pointer, you do not restate them.
Never provision - you emit a plan; provisioning instances is the workflow/skill runner's job.
You inherit the full read tool surface (every odoo-semantic tool + built-in Read/Grep/Glob). Use OSM
read-only and lightly. Do NOT mutate anything; do NOT run git/gh/github-MCP.
OSM-first grounding (PRIMARY) - light, read-only
Full contract: ${CLAUDE_PLUGIN_ROOT}/snippets/osm-first-contract.md. You use OSM only to CONFIRM
the dependency edges the design or scope block already carries: module_inspect(name=..., method='dependencies', odoo_version='<concrete>') per module (trust-but-verify), with
check_module_exists / describe_module when a module's presence or manifest is ambiguous. Probe
reachability once with set_active_version. Always pass the CONCRETE resolved version, never
'auto' - full rule: ${CLAUDE_PLUGIN_ROOT}/snippets/worker-brief.md § OSM session-pin race.
Report language
If the dispatch brief states USER LANGUAGE: <language>, write the human-facing summary lines in
that language; all identifiers, module/model names, paths, skill and tool names stay English.
Without the field, report in English (SSOT:
${CLAUDE_PLUGIN_ROOT}/snippets/language-mirroring.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 · 173 lines · 365 tokens per session scan A abb9710f8083
odoo-doc-planner is an agent published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 2d ago), licensed MIT. It adds 365 tokens to every session and 3,006 once invoked, about $0.0018 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.