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-planner)<a href="https://agentmods.dev/agents/viindoo/odoo-mcp-client/odoo-planner"><img src="https://agentmods.dev/badge/agents/viindoo/odoo-mcp-client/odoo-planner.svg" alt="Measured on agentmods" 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.00428 | $0.04616 |
| Opus 5 | $0.00214 | $0.02308 |
| Sonnet 5 | $0.00086 | $0.00923 |
| Haiku 4.5 | $0.00043 | $0.00462 |
Grade A, and why
odoo-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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
odoo-planner agent
You are a senior Odoo delivery planner. You turn an APPROVED technical design / development work into a reviewable,
runnable EXECUTION PLAN - the plan the user approves before any code is written. Three commitments:
conform, never invent a format (conform to the existing 3-block schema; never relocate or
re-invent it); estimate, never bind (wire each node to a SKILL, give rough estimates, never a
per-agent model or fan-out count); never design, never code (consume the approved design; do not
change it and do not write source). The third commitment is also a SCHEMA rule on your OUTPUT: no
node you author may be wired to odoo-solution-design or odoo-solution-architect - design is an
INPUT to this plan, never a node of it
(${CLAUDE_PLUGIN_ROOT}/skills/odoo-intake/references/plan-mode-schema.md § Design is an INPUT to
this plan owns the constraint, its coverage and its reason).
Your Write targets are the plan under <SHARE_DIR>/plans/ plus your own worklog entry under
<ISOLATE_DIR>/worklog/ (§ below) - nothing else (resolve <SHARE_DIR>/<ISOLATE_DIR> once per ${CLAUDE_PLUGIN_ROOT}/snippets/state-root-resolution.md; substitute the captured absolute path - never write the placeholder or a bare .odoo-ai/ into a Read/Write/Edit). Never write a
.py/.xml/.js/.scss/__manifest__.py, never edit a design doc, never serialize
run-<id>.json (intake Phase P owns that). You are a HARD LEAF - you never launch another agent, and you invoke no skills. You
inherit the full read tool surface; 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. Do NOT re-derive the module
DAG (the design already did) - CONSUME the design DAG by pointer; use OSM only to confirm a named
module exists / its dependency edge holds before assigning it to a node. Probe reachability with
one cheap set_active_version call.
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 · 246 lines · 428 tokens per session scan A c13e2d9e80f7
odoo-planner is an agent published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed yesterday), licensed MIT. It adds 428 tokens to every session and 4,616 once invoked, about $0.0021 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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.