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-planning)<a href="https://agentmods.dev/skills/viindoo/odoo-mcp-client/odoo-planning"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-planning/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-planning"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-planning.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.00210 | $0.06744 |
| Opus 5 | $0.00105 | $0.03372 |
| Sonnet 5 | $0.00042 | $0.01349 |
| Haiku 4.5 | $0.00021 | $0.00674 |
Grade A, and why
odoo-planning 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 6d 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 — 401 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Odoo Planning - the execution plan between design and code
Where this sits in the flow (planning follows design, precedes code)
Planning step only. Output: <SHARE_DIR>/plans/<slug>-<date>.md (resolve <SHARE_DIR>/<ISOLATE_DIR>
via the resolve-capture-substitute protocol in ${CLAUDE_PLUGIN_ROOT}/snippets/state-root-resolution.md
before the first Read/Write/Edit of a state-root path in this skill; gitignored, L1) - never production
source. Correct order:
gap/brl -> odoo-solution-design (TDD + index.yaml) -> HUMAN approves design
-> odoo-planning -> {odoo-planner (code plan) + odoo-doc-planner (doc plan)}
-> ONE lifecycle plan gate -> ExitPlanMode
-> intake Phase P serializes run-<id>.json -> run-harness drives the node plan
-> doc stage (user-doc + marketing-doc) executes after code/review/QA
This skill does NOT compute either plan itself and does NOT write code - it dispatches TWO
planners (odoo-planner for code, odoo-doc-planner for doc) and owns the approve /
ExitPlanMode handoff. odoo-solution-design decides HOW to build; odoo-planning decides HOW TO
SHIP (node build order, landing sequence, doc cluster schedule, full lifecycle).
Note: odoo-doc-planner also runs STANDALONE via odoo-doc-illustration / module-packaging
for doc-only work on existing modules - odoo-planning is NOT the only path to it.
Role
Odoo delivery planner. Turns an approved technical design into ONE lifecycle plan covering the full product journey - code-build AND doc. Dispatches TWO leaf planners in sequence:
odoo-planner(code-build plan): a dependency-ordered node graph, each node wired to a SKILL, driven end to end byrun-harness's single node loop. Pure code-build planner - no doc-logic.odoo-doc-planner(doc-package plan): dependency clusters, branch-aware instance allocation, per-instance incremental install-doc-verify-commit order, dedup, parallelism schedule; covers user-guide (doc/index.rst) AND marketing landing (static/description/index.html). Runs withplan_source: design-dag- reuses the approved design DAG; does NOT re-derive it.
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.
- 6d ago First seen · 401 lines · 210 tokens per session scan A 0808bdf3148e
odoo-planning is a skill published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 3d ago), licensed MIT. It adds 210 tokens to every session and 6,744 once invoked, about $0.0011 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.