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/commands/viindoo/odoo-mcp-client/odoo-draft-followup)<a href="https://agentmods.dev/commands/viindoo/odoo-mcp-client/odoo-draft-followup"><img src="https://agentmods.dev/badge/commands/viindoo/odoo-mcp-client/odoo-draft-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/commands/viindoo/odoo-mcp-client/odoo-draft-followup"><img src="https://agentmods.dev/badge/commands/viindoo/odoo-mcp-client/odoo-draft-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.00055 | $0.02005 |
| Opus 5 | $0.00028 | $0.01002 |
| Sonnet 5 | $0.00011 | $0.00401 |
| Haiku 4.5 | $0.00006 | $0.00200 |
Grade C, and why
odoo-draft-followup scanned grade C with 1 finding 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 10d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
find <ISOLATE_DIR>/followups/ -maxdepth 1 -type f -name '*.md' -mmin +43200 -exec rm -rf {} + How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/odoo-draft-followup
Single-purpose slash command for sales follow-up email drafting. Chains the odoo-deal-followup skill with an explicit save-to-file step, gating on user approval before writing to disk.
When to use
Invoke when you have a stalled or at-risk deal and need a follow-up email today. The skill analyzes deal context, assesses risk, suggests a next-best action, then drafts an email for review before sending.
Type: /odoo-draft-followup [customer-label]
Optional: supply customer label on the command line (e.g., Customer A). If omitted, the command will prompt you for it.
Hard rules
- Deal context is a request input: CRM metadata and pipeline rules arrive in the request itself (orchestrator structured data, or the sales user stating them). Nothing on disk stores them - do not go looking for a file. Resolve
<SHARE_DIR>/<ISOLATE_DIR>once per${CLAUDE_PLUGIN_ROOT}/snippets/state-root-resolution.mdbefore writing the draft; substitute the captured absolute path - never write the placeholder or a bare.odoo-ai/into a Read/Write/Edit. When a fact about the customer's Odoo deployment matters, resolve the series per${CLAUDE_PLUGIN_ROOT}/snippets/project-facts-resolution.md. - Use what the caller already gave, then ask only for gaps: deal details are usually already in the request. Never make a human retype what is present. Optionally enrich from a live CRM/ERP/email integration if one exists - but never assume one; this command must work for an agent with only the request text and local files. Ask only for fields still unresolved:
- Customer label or short name (e.g., "ABC Manufacturing")
- Last touch date - only if not already provided
- Current pipeline stage - only if not already provided
- Prior commitments or blockers (e.g., "waiting on PO", "evaluating competing offer")
- Gate before saving: Display the drafted email to the user. Explicitly ask: "Email draft OK? (approve / refine: [feedback] / cancel)" - the PLAN gate set (
${CLAUDE_PLUGIN_ROOT}/snippets/planning-gate-contract.md). Do not write to disk unless the user confirms "approve". - No auto-send: This command only drafts. It does not send email, update CRM systems, or trigger workflows.
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.
- 10d ago First seen · 123 lines · 55 tokens per session scan C 5475686de31d
odoo-draft-followup is a command published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 3d ago), licensed MIT. It adds 55 tokens to every session and 2,005 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.