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-competitive-brief)<a href="https://agentmods.dev/skills/viindoo/odoo-mcp-client/odoo-competitive-brief"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-competitive-brief/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-competitive-brief"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-competitive-brief.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.00230 | $0.03346 |
| Opus 5 | $0.00115 | $0.01673 |
| Sonnet 5 | $0.00046 | $0.00669 |
| Haiku 4.5 | $0.00023 | $0.00335 |
Grade A, and why
odoo-competitive-brief 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 11d 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 — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Strategist / CEO needing board-ready competitive intelligence - usable in board decks, investor updates, or strategy sessions. The CEO is the primary intelligence source; this skill structures and prioritizes what the user already knows. It does NOT invent competitive facts.
Scope is elastic (mirrors odoo-addon-diff's elastic scope). The default is the full board
brief below (Rounds 0-5, 5-10 dimension capability matrix, GTM moves, threat assessment,
recommended response). When the ask is narrower - ONE named feature only, not a landscape/GTM/
threat review (e.g. odoo-position-feature dispatches this skill for a single feature's Odoo-vs-
competitor check) - scale down to single-feature mode: skip the GTM (Round 3) and threat
(Round 4) machinery and emit just the compact 2-column matrix in "Single-feature mode" under
Output format. Full-brief output stays the default whenever scope is unspecified or spans more
than one feature/dimension.
Out of Scope
| User intent | Route to |
|---|---|
| Sales objection handling ("they say Odoo can't do X") | odoo-objection-handling |
| Feature comparison drill-down between Odoo versions | odoo-version-diff |
| Detailed module/add-on diff | odoo-addon-diff |
| Marketing copy or campaign messaging | odoo-content-draft / odoo-campaign-plan |
| Single feature availability check | odoo-feature-check |
| Customer requirements gap analysis | odoo-gap-analysis |
MCP tools
Optional - call only when grounding "your platform has X" or "Odoo can't do Y" claims:
profile_inspect- Profile-level introspection (method='summary'|'repos'|'modules'): inheritance chain + repos + indexed module count/list for your platform profile. Use it to fill the "your platform" column of the Round 2 capability matrix with indexed fact instead of training-data assertion (the board-facing reason this matters).check_module_exists- Verify that a module or feature exists in your platform (CE/EE/custom distribution), used to substantiate or refute capability claims a competitor makes in their messaging. Call when the user says "competitor claims Odoo lacks X - is that true?".find_examples- Semantic code search returning real indexed code snippets from the Odoo codebase, used when a competitor's marketing claims "Odoo cannot do Y" and the CEO needs concrete proof-of-existence before a board meeting.
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.
- 11d ago First seen · 308 lines · 230 tokens per session scan A 638d6b53915f
odoo-competitive-brief is a skill published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 4d ago), licensed MIT. It adds 230 tokens to every session and 3,346 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-08-31.
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…