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-solution-design)<a href="https://agentmods.dev/skills/viindoo/odoo-mcp-client/odoo-solution-design"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-solution-design/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/skills/viindoo/odoo-mcp-client/odoo-solution-design"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-solution-design.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.00245 | $0.08344 |
| Opus 5 | $0.00122 | $0.04172 |
| Sonnet 5 | $0.00049 | $0.01669 |
| Haiku 4.5 | $0.00024 | $0.00834 |
Grade A, and why
odoo-solution-design 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 5d 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 — 474 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Where this sits in the flow (design precedes the code Plan Mode)
Planning/analysis step only. Output: <SHARE_DIR>/designs/… (gitignored, L1; resolve <SHARE_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
production source. Correct order:
design (architect writes the TDD) → HUMAN approves the design → Plan Mode for the code → code → review
The approved TDD is the plan the code Plan Mode executes; do not flip this order.
Input port - gap-analysis artifact (read before designing)
Before dispatching the architect, look for a gap-analysis artifact on disk - the per-requirement classification/effort is the design PRECONDITION, read it; do NOT re-derive the tier from conversational text:
- Glob
<SHARE_DIR>/gap-analysis/*/gap-matrix.jsonl(newest dir wins); the consultant path may instead carry BRL output under<SHARE_DIR>/brl/*/- accept either source. - Found: READ it. Each
gap-matrix.jsonlline is one requirement with keysreq_id·requirement·coverage(full|partial|none) ·classification(standard|config|extension|custom) ·effort_tier(S|M|L|XL) ·module·grounded·notes. Useclassification+effort_tierper requirement to decide WHICH requirements need a TDD and at what depth (extension/custom + L/XL drive the design; standard/config with a single obvious approach skip DESIGN and route straight toodoo-planninginstead - planning is mandatory for all work, see "Skip DESIGN for trivial work" below). Cite the artifact path in the design doc and pass it to the architect (GAP_MATRIX:line in the P1 template). When the artifact exists it is authoritative - do NOT re-derive tiers from memory. - Not found AND the change is non-trivial: recommend running
odoo-gap-analysisfirst to classify/cost the requirements rather than guessing the tier. Not finding one is NOT a blocker: dispatch the architect with theGAP_MATRIX:line omitted and it measures the scope itself before designing (agents/odoo-solution-architect.md§ Round 1 - Gather context). Running the gap analysis here first is still preferable when a human wants to gate the cost separately - it is a sequencing choice, never a precondition you stall on. (Trivial single-approach change: proceed without it.)
What ships with it
3 files 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.
- 5d ago First seen · 474 lines · 245 tokens per session scan A da8ae4106300
odoo-solution-design is a skill published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 2d ago), licensed MIT. It adds 245 tokens to every session and 8,344 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…