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.00043 | $0.00869 |
| Opus 5 | $0.00022 | $0.00434 |
| Sonnet 5 | $0.00009 | $0.00174 |
| Haiku 4.5 | $0.00004 | $0.00087 |
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 9d 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 — 66 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
All phase definitions, gates, model tiers, skills, 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), fallback policy, and resume logic live in the workflow YAML. 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 (optional version range such as v16-to-v17 or
16.0-17.0). Because that workflow declares an on_complete cross-workflow chain, intake MUST engage
Phase P (trigger 3: a single workflow node whose YAML declares on_complete) - serializing a 1-node
RUN-DAG and dispatching the run-harness above it. The run-harness then dispatches workflow-chaining,
which reads the workflow YAML, collects missing inputs (source version, target version, scope,
deadline), emits the soft-plan-gate, and executes the four-phase pipeline:
risk-overview -> deprecation-audit -> version-diff -> synthesis
Output is written to <ISOLATE_DIR>/upgrade-plans/ on explicit user confirmation at the final gate. Do NOT
dispatch workflow-chaining directly - without the run-harness above it, the on_complete design
handoff degrades to a human suggestion (see below).
Design handoff (on_complete). When the plan contains migration/refactor items with more than one
viable approach (needs_design == true), on_complete chains to odoo-solution-design so those items
are designed before any code is written. Routing through /odoo-intake Phase P keeps the run-harness
present to read the emitted Continuation Contract and auto-advance - the chain fires automatically. A
bare workflow-chaining dispatch (no run-harness) degrades this to a visible human suggestion, which is
why this command routes via intake.
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.
- 9d 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 (7 stars, last pushed 3d ago), licensed MIT. It adds 43 tokens to every session and 869 once invoked, about $0.0002 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 commands, from other repositories
init
Initialize configurations for Supabase local development.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
api-contract-review
Review an API contract (endpoints, request/response shapes, error codes, auth model) BEFORE implementation for naming consistency, versioning, pagination, idempotency, and alignment with existing endpoints. Distinct from review-hard (post-implementation risk) and repo-consistency-sweep (pattern matching on written…
build
Discover an AI Gateway's models and MCP tools, retrieve a credential, and integrate them into your app — call a model, connect MCP tools, or scaffold a runnable agent.
fastapi
FastAPI application design and implementation conventions. Use this skill when building, updating, or reviewing FastAPI services, routers, dependencies, request/response schemas, streaming endpoints, or API tests. Trigger on FastAPI-specific work such as path operation design, dependency injection, response models…