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/commands/viindoo/odoo-mcp-client/odoo-plan-upgrade)<a href="https://agentmods.dev/commands/viindoo/odoo-mcp-client/odoo-plan-upgrade"><img src="https://agentmods.dev/badge/commands/viindoo/odoo-mcp-client/odoo-plan-upgrade/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/commands/viindoo/odoo-mcp-client/odoo-plan-upgrade"><img src="https://agentmods.dev/badge/commands/viindoo/odoo-mcp-client/odoo-plan-upgrade.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.00020 | $0.00554 |
| Opus 5.5 | $0.00008 | $0.00222 |
| Sonnet 5.5 | $0.00004 | $0.00111 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
odoo-plan-upgrade 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 20d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/odoo-plan-upgrade
Thin dispatcher for the declarative odoo-plan-upgrade workflow.
SSOT: plugins/odoo-ai-agents/workflows/odoo-plan-upgrade.workflow.yaml holds the phase
definitions, model tiers, skills, fallback policy and resume logic, and the output directory
<ISOLATE_DIR>/upgrade-plans/ (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). Do not duplicate them
here.
Dispatch
Yield to the odoo-intake skill with the intent already resolved: run the odoo-plan-upgrade
workflow over this command's $ARGUMENTS (an optional version range, <from>-to-<to> or
<from>-<to>). Intake MUST engage Phase P (trigger 3: a single workflow node whose YAML declares
on_complete), serializing a 1-node RUN-DAG and running it (plan-mode-schema.md § Running the
plan). The runner dispatches workflow-chaining, which reads the workflow YAML, collects missing
inputs (source version, target version, scope, deadline), decides the workflow plan, and executes:
risk-overview -> deprecation-audit -> version-diff -> synthesis
Do NOT dispatch workflow-chaining directly: without a run above it, the on_complete design
handoff (needs_design == true chains to odoo-solution-design) degrades to a human suggestion.
Execute handoff. For the code-level upgrade once this plan is approved, invoke
odoo-modules-upgrade (skill) manually; it is not auto-dispatched and this plan writes no code.
When to use
- A client asks for a full upgrade plan covering risk, deprecation, and API diff in one deliverable.
- You need an executive-readable risk overview and dev-readable action items in one artifact.
Do not use when only a deprecation check is needed (odoo-deprecation-audit) or only an API
diff is needed (odoo-version-diff).
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.
- 20d ago Changed · -20 lines a74123783820
- 24d ago Changed ba2ac5f2af1f
- 1mo ago Changed · -23 tokens per session 95305f5f9807
- 2mo ago First seen · 66 lines · 43 tokens per session scan A 471d23e61d15
odoo-plan-upgrade is a command published in the GitHub repository Viindoo/odoo-mcp-client (9 stars, last pushed 2d ago), licensed MIT. It adds 20 tokens to every session and 554 once invoked, about $0.0001 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-plan-upgrade compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| odoo-plan-upgradeViindoo/odoo-mcp-client | Command | 9 | 2d ago | MIT | A | 20 | Claude Code |
| initfcakyon/claude-codex-settings | Command | 1.2k | yesterday | Apache-2.0 | A | 0 | Claude Code |
| http-serviceMadAppGang/magus | Command | 14 | today | MIT | A | 27 | Claude Code |
| api-contract-reviewMozurok/fhorja.dev | Command | 10 | 1mo ago | MIT | A | 64 | Claude Code |
| buildAzure/ai-gateway | Command | 5 | 13d ago | MIT | A | 0 | Claude Code |
| start-10-1minicoohei/ai-agent-camp | Command | 348 | 1mo ago | none | A | 2 | Claude Code |
| fastapimfmezger/ai_agent_dotfiles | Command | 7 | 3mo ago | MIT | A | 84 | Claude Code, Gemini CLI |