What is odoo-feature-check?

An evidence-based checker for whether standard Odoo already provides one requested feature. It reports the relevant module, edition, fields, and models, where CE means Community Edition and EE means Enterprise Edition.

Use it to answer a single yes-or-no availability question for a specific Odoo version and edition.

It helps developers and consultants avoid proposing custom work when the feature already exists, and makes the answer easier to support with evidence.

odoo-feature-check — Skill for Claude Code by Viindoo/odoo-mcp-client

Install

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.

Claude Code

/plugin marketplace add Viindoo/odoo-mcp-client

Claude Code

/plugin install odoo-ai-agents

Made for: Claude Code.

Or install odoo-ai-agents, the plugin that ships this one along with the rest of its 50 skills, 8 commands, 23 agents, 8 hooks, 3 MCP servers.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-feature-check/github.svg)](https://agentmods.dev/skills/viindoo/odoo-mcp-client/odoo-feature-check)

Your own site

<a href="https://agentmods.dev/skills/viindoo/odoo-mcp-client/odoo-feature-check"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-feature-check/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/viindoo/odoo-mcp-client/odoo-feature-check"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-feature-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,006 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00021	$0.02006
Opus 5.5	$0.00008	$0.00802
Sonnet 5.5	$0.00004	$0.00401
Haiku 4.5	$0.00002	$0.00201

Measured 17d ago against content hash 7fe77891760b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

odoo-feature-check 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 17d 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.

plugins/odoo-ai-agents/skills/odoo-feature-check/SKILL.md · 121 lines

How it starts

The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Role

Consultant / Developer

Out of Scope

Multi-requirement effort matrix → use odoo-gap-analysis
CE vs EE three-way comparison → use odoo-addon-diff
Customer-facing objection response → use odoo-objection-handling
COMPLETE enumeration of ALL features a module ships (for documentation) -> use odoo-doc-feature-map. This skill answers ONE feature yes/no availability question; it does NOT enumerate the full capability set of a module

MCP tools

Pick the right tool first. Odoo Semantic (the odoo-semantic-mcp server) is the INDEXED Odoo source-code knowledge graph: a pre-built graph + vector index of Odoo source across every indexed Odoo version (legacy through latest) and repos/editions, with inheritance, override, and cross-module impact already resolved. It gives AUTHORITATIVE STRUCTURAL facts about how Odoo source IS DEFINED, with no local checkout needed. Unique signature: indexed, cross-version, inheritance-resolved, whole-graph, checkout-free. It is a STATIC index with NO runtime/live data.

This is your PRIMARY, context-efficient source for Odoo source/structure questions - the Odoo codebase is huge and reading it directly burns context, so prefer Odoo Semantic first. Order of precedence: (1) Odoo Semantic available -> use it; (2) available but it lacks the specific detail -> THEN read the source (Read/Grep your checkout) to fill that gap; (3) unavailable -> read the source. Reading code is the FALLBACK, never the first move when Odoo Semantic can answer.

Do NOT use Odoo Semantic for:

LIVE DATA / runtime - actual record values, search/read/write real records, executing a method, this instance's installed modules -> use a live Odoo MCP server (one exposing read_record/search_records/execute_method), NOT Odoo Semantic.

Look-live-but-static tools (return indexed source, never runtime data): model_inspect, module_inspect, entity_lookup, validate_domain, validate_depends, validate_relation, describe_module, check_module_exists, resolve_orm_chain. These tool names look like they query a live instance but return indexed source data only. If you need live records, Odoo Semantic is the wrong server.

Read the full file on GitHub · 121 lines

Changes

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.

17d ago Changed 7fe77891760b
24d ago Changed 57099931ba39
1mo ago Changed 5bffcac80fac
1mo ago Changed · -10 lines · -186 tokens per session 1213045aabd3
2mo ago First seen · 131 lines · 207 tokens per session scan A c739b717c6c8

Subscribe to this mod's changes

odoo-feature-check is a skill published in the GitHub repository Viindoo/odoo-mcp-client (9 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 2,006 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-09-03.

Research

odoo-feature-check next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
odoo-feature-checkViindoo/odoo-mcp-client	Skill	9	2d ago	MIT	A	21	Claude Code
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	100k	today	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	3d ago	MIT	A	200	Claude Code, Codex
browser-automationopenclaw/openclaw	Skill	394k	today	MIT	A	36	Claude Code
systematic-debuggingobra/superpowers	Skill	315k	6d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code