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-rfp-response)<a href="https://agentmods.dev/skills/viindoo/odoo-mcp-client/odoo-rfp-response"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-rfp-response/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-rfp-response"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-rfp-response.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.00018 | $0.03078 |
| Opus 5.5 | $0.00007 | $0.01231 |
| Sonnet 5.5 | $0.00004 | $0.00616 |
| Haiku 4.5 | $0.00002 | $0.00308 |
Grade A, and why
odoo-rfp-response 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 24d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Pre-sales Consultant / Bid Manager
When to use
- Prospect / public-sector client issues an RFP / RFQ / ITT expecting a formal compliance verdict per line
- You need a written compliance matrix before submitting a full proposal
- Sales engineering needs a quick score card to decide whether to bid
- Project manager needs to flag which requirements need custom dev before committing to a timeline
Difference from siblings: odoo-gap-analysis outputs effort tiers (days) for quoting; this skill outputs compliance verdicts. odoo-capability-proof gives deep code evidence for ONE requirement; this skill covers ALL requirements at once. odoo-feature-check handles a single feature; this skill handles a numbered list.
Out of Scope
- Effort estimation / day-count →
odoo-gap-analysis - Deep code-level proof for a single requirement →
odoo-capability-proof - Single feature availability outside RFP context →
odoo-feature-check - Narrative sections of the full proposal →
odoo-content-draft - Objection handling after RFP submission →
odoo-objection-handling - A full end-to-end bid response package (discovery synthesis + gap analysis + capability proof +
objection pre-empt + proposal draft), not just this compliance matrix →
/odoo-respond-bid
MCP tools
Pick the right tool first. Odoo Semantic (the odoo-semantic-mcp server) is the INDEXED Odoo source-code knowledge graph: a pre-built graph + vector index of Odoo source across every indexed Odoo version (legacy through latest) and repos/editions, with inheritance, override, and cross-module impact already resolved. It gives AUTHORITATIVE STRUCTURAL facts about how Odoo source IS DEFINED, with no local checkout needed. Unique signature: indexed, cross-version, inheritance-resolved, whole-graph, checkout-free. It is a STATIC index with NO runtime/live data.
This is your PRIMARY, context-efficient source for Odoo source/structure questions - the Odoo codebase is huge and reading it directly burns context, so prefer Odoo Semantic first. Order of precedence: (1) Odoo Semantic available -> use it; (2) available but it lacks the specific detail -> THEN read the source (Read/Grep your checkout) to fill that gap; (3) unavailable -> read the source. Reading code is the FALLBACK, never the first move when Odoo Semantic can answer.
Do NOT use Odoo Semantic for:
- LIVE DATA / runtime - actual record values, search/read/write real records, executing a method, this instance's installed modules -> use a live Odoo MCP server (one exposing read_record/search_records/execute_method), NOT Odoo Semantic.
Look-live-but-static tools (return indexed source, never runtime data):
model_inspect,module_inspect,entity_lookup,validate_domain,validate_depends,validate_relation,describe_module,check_module_exists,resolve_orm_chain. These tool names look like they query a live instance but return indexed source data only. If you need live records, Odoo Semantic is the wrong server.
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.
- 24d ago Changed 55e01501cfe0
- 1mo ago Changed fa57a770dbcc
- 1mo ago Changed · -8 lines · -203 tokens per session 0927907af49e
- 2mo ago First seen · 182 lines · 221 tokens per session scan A e7a20fc38039
odoo-rfp-response is a skill published in the GitHub repository Viindoo/odoo-mcp-client (9 stars, last pushed 2d ago), licensed MIT. It adds 18 tokens to every session and 3,078 once invoked, about $0.0001 per session on Opus 5.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.
odoo-rfp-response compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| odoo-rfp-responseViindoo/odoo-mcp-client | Skill | 9 | 2d ago | MIT | A | 18 | Claude Code |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 100k | today | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 3d ago | MIT | A | 200 | Claude Code, Codex |
| browser-automationopenclaw/openclaw | Skill | 394k | today | MIT | A | 36 | Claude Code |
| systematic-debuggingobra/superpowers | Skill | 315k | 6d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |