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/skills/viindoo/odoo-mcp-client/odoo-instance)<a href="https://agentmods.dev/skills/viindoo/odoo-mcp-client/odoo-instance"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-instance.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.00247 | $0.09782 |
| Opus 5 | $0.00123 | $0.04891 |
| Sonnet 5 | $0.00049 | $0.01956 |
| Haiku 4.5 | $0.00025 | $0.00978 |
Grade A, and why
odoo-instance 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 3d 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 — 454 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Odoo instance lifecycle coordinator. Front door for ALL instance lifecycle operations (create,
drop, park, resume, init, update, run-tests, ensure-up, status, load-language) for every Odoo
series the index carries - resolve that set with list_available_versions(), never from a
remembered floor.
Keeps the caller's context clean by delegating shell-level work and relaying a structured result
block. Programmatic twin of the interactive /odoo-setup command (the human declare-and-spinup
wizard that writes instances.toml): use this skill when the caller already knows the operation
parameters - hand them over, get back a structured instance-ops block.
Single owner of instance provisioning. This skill is the SINGLE PLACE that OWNS Odoo instance
fan-out: any component needing a live instance routes here via the Skill tool instead of driving
the lifecycle itself, so the L2 human gate, instance-allocation rules, and HARD RULES (en_US
union, Viindoo to_base, the GATE_ROLE-conditioned lint-module install, per-version cli_help
grounding) are enforced in one place. When the caller is a declared HARD LEAF (agents.<name>.role == leaf in the
agent-role SSOT, generator/skill_tool_deps.json), this skill MUST provision INLINE (see "Inline
leaf-mode" below) and MUST NOT launch the odoo-instance-ops agent - inline leaf-mode is
mandatory for a leaf caller, not a judgment call. For a spawner/coordinator/skill caller, provision
the way that fits the caller's context - run the ops steps INLINE in the caller's own context (see
"Inline leaf-mode" below), or launch the odoo-instance-ops agent per "Brief shape" below; this
skill is the component that owns launching that agent. However the
operation is carried out, the SAME HARD RULES apply - the inline path is not a bypass. A provided
INSTANCE_HANDLE ALWAYS wins over self-provisioning either way (contract:
${CLAUDE_PLUGIN_ROOT}/snippets/instance-handle-contract.md). scripts/lib/allocator.py is never
how a caller PROVISIONS an instance: both paths below reach it only after running the HARD RULES,
so an acquire that routed around this skill is an acquire that skipped them. Tearing your OWN
lease down at your terminal status - releasing or parking it - is not provisioning and is run
directly, per ${CLAUDE_PLUGIN_ROOT}/snippets/resource-teardown-contract.md T1.
The odoo-instance-ops agent runs at a flat sonnet tier when launched - there is no
per-operation model-tier table.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 454 lines · 247 tokens per session scan A b6cf45136d04
odoo-instance is a skill published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 4d ago), licensed MIT. It adds 247 tokens to every session and 9,782 once invoked, about $0.0012 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-09-03.
Other skills, from other repositories
omni-mcp
Connect to the OmniRoute MCP server (110 tools, 3 transports: SSE/stdio/HTTP). Covers routing, cache, compression, memory, skills, providers, and audit tools across 33 permission scopes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.