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-discovery-summary)<a href="https://agentmods.dev/skills/viindoo/odoo-mcp-client/odoo-discovery-summary"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-discovery-summary/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-discovery-summary"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-discovery-summary.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.00238 | $0.02227 |
| Opus 5 | $0.00119 | $0.01113 |
| Sonnet 5 | $0.00048 | $0.00445 |
| Haiku 4.5 | $0.00024 | $0.00223 |
Grade A, and why
odoo-discovery-summary 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Discovery-notes synthesis for Sales AE and Pre-Sales Consultant work (dual role). Output audience: AEs handing a brief to a solution architect or manager, and pre-sales consultants qualifying fit before demo time.
Out of Scope
- Proposal/quote →
odoo-gap-analysis(effort matrix) /odoo-respond-bid - Follow-up email to prospect →
odoo-deal-followup - Handling a specific objection →
odoo-objection-handling - Single feature lookup outside discovery →
odoo-feature-check
MCP tools
OSM is OPTIONAL - this skill is standalone-first. Only call OSM tools when the user explicitly wants to verify Odoo can address a stated pain, or requests "double-check with Odoo" / "kiem tra Odoo co chua".
Optional - pain-point verification:
check_module_exists- When a customer named a specific feature need (e.g., "lot traceability", "subscription billing"), call to verify whether Odoo has a standard module for it and which edition. Include result in the Fit Assessment table.find_examples- When the customer wants proof-of-concept evidence during or after discovery ("can you show me how Odoo does X?"), use to surface real indexed code snippets or UI evidence. Only call if user explicitly requests it.profile_inspect- When several Confidence-Low fit rows turn on "does the Viindoo profile cover this vertical" (e.g. is there aviin_mrp_*family?), callprofile_inspect(method='modules', name=<profile>, odoo_version='<version>')once to list the profile-owned modules - this resolves several fit rows in a single call instead of onecheck_module_existsper module.
Do NOT call set_active_profile, model_inspect, lint_check, or any
developer-oriented tools - this skill outputs business analysis, not code.
Standalone-first fallback
This skill produces a full Discovery Profile without OSM. Follow rounds in sequence.
Round 0 - Resolve project facts
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.
- 9d ago First seen · 185 lines · 238 tokens per session scan A d8e75353be6e
odoo-discovery-summary is a skill published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 6d ago), licensed MIT. It adds 238 tokens to every session and 2,227 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.