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-deal-followup)<a href="https://agentmods.dev/skills/viindoo/odoo-mcp-client/odoo-deal-followup"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-deal-followup/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-deal-followup"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-deal-followup.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.00249 | $0.01949 |
| Opus 5 | $0.00125 | $0.00975 |
| Sonnet 5 | $0.00050 | $0.00390 |
| Haiku 4.5 | $0.00025 | $0.00195 |
Grade A, and why
odoo-deal-followup 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 12d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Follow-up drafting for a solo go-to-market seller (Sales AE or founder, no SDR or sales team). Audience: a prospect or customer in an active B2B deal. Purpose: prevent deals going cold from missed follow-ups or unclear next steps - every open deal warrants a timely, specific touch.
Out of Scope
- Discovery session summary / demo notes →
odoo-discovery-summary - Responding to technical objections →
odoo-objection-handling - Proving a feature with code evidence →
odoo-capability-proof - Simple feature lookup →
odoo-feature-check - Gap analysis / effort estimate →
odoo-gap-analysis
MCP tools
This skill is standalone-first - OSM/MCP is OPTIONAL. Most invocations do not need MCP.
OSM usage rule: Only invoke when the user explicitly asks to fact-check a specific Odoo feature claim in the email or deal context. Do not call MCP automatically just because the deal involves Odoo.
Optional tool (on-demand only):
check_module_exists- Verify whether a specific Odoo module/feature exists and in which edition (CE/EE/your custom distribution). Call only when user asks to fact-check a feature claim present in the deal thread or email. Do NOT call speculatively.
This skill performs text analysis and email composition directly - no code generation or external model delegation is involved.
Standalone-first fallback
Skill always operates without OSM. All logic runs on user-provided text.
Round 0 - Resolve project facts, then ask only for gaps
- Use the invocation context first. Deal details are usually already in the request - do not re-ask for anything already provided.
- Resolve project facts. Resolve the Odoo series per
${CLAUDE_PLUGIN_ROOT}/snippets/project-facts-resolution.md. CRM defaults are request or brief inputs - never assume them. - Optional enrichment: If a live CRM/email integration is available, enrich from it - but treat as a bonus, never required. Skill must work with only request text + local files.
- Ask only for fields still unresolved after steps 1-3, in one message.
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.
- 12d ago First seen · 176 lines · 249 tokens per session scan A b3e8d3cc4118
odoo-deal-followup is a skill published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 6d ago), licensed MIT. It adds 249 tokens to every session and 1,949 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-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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…