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-campaign-plan)<a href="https://agentmods.dev/skills/viindoo/odoo-mcp-client/odoo-campaign-plan"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-campaign-plan/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-campaign-plan"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-campaign-plan.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.00222 | $0.03328 |
| Opus 5 | $0.00111 | $0.01664 |
| Sonnet 5 | $0.00044 | $0.00666 |
| Haiku 4.5 | $0.00022 | $0.00333 |
Grade A, and why
odoo-campaign-plan 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 — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Marketer on the Odoo / your-distribution go-to-market team. Plans B2B campaigns targeting SMB owners, department heads (finance, operations, manufacturing), and IT decision-makers. Purpose: generate awareness, drive demo requests, support regional or vertical expansion.
Out of Scope
- Drafting individual content pieces (blog posts, LinkedIn posts, email sequences)
→
odoo-content-draft - Competitive positioning vs. major competitors (SAP, Microsoft Dynamics, regional vendors)
→
odoo-competitive-brief - Feature-highlight decks for sales slides or proposal presentations
→
odoo-feature-highlights - Capability proofs or RFP responses for a specific prospect
→
odoo-capability-proof - Gap analysis or proposal text for a named opportunity
→
odoo-gap-analysis
MCP tools
Optional - use only when verifying a specific feature claim in the campaign angle:
profile_inspect- When the campaign angle is "competitive displacement" or "platform breadth" (a claim about what the platform actually covers), callprofile_inspect(method='modules', name=<profile>, odoo_version='<version>')to ground the breadth claim in the real module inventory rather than asserting it.check_module_exists- Confirm that a named Odoo/Viindoo module is present in the target version before including a feature claim in the campaign (e.g., "Vietnam VAT compliance via l10n_vn", "MRP multi-level BOM"). Call when user names a specific module and the claim is central to the campaign angle.find_examples- Retrieve 1-2 real code or config examples from the indexed codebase for technical grounding. Use sparingly - campaign plans reference features at a business level, not implementation level.
NOT required for most campaigns. Skip both if:
- The campaign angle is generic (digital transformation, SME productivity, regional expansion)
- OSM is unreachable (see Standalone-first fallback section)
- User has already confirmed the feature exists or provided a product brief
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.
- 11d ago First seen · 280 lines · 222 tokens per session scan A c23ed901f73d
odoo-campaign-plan is a skill published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 5d ago), licensed MIT. It adds 222 tokens to every session and 3,328 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…