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-respond-bid)<a href="https://agentmods.dev/commands/viindoo/odoo-mcp-client/odoo-respond-bid"><img src="https://agentmods.dev/badge/commands/viindoo/odoo-mcp-client/odoo-respond-bid/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-respond-bid"><img src="https://agentmods.dev/badge/commands/viindoo/odoo-mcp-client/odoo-respond-bid.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.00056 | $0.00638 |
| Opus 5 | $0.00028 | $0.00319 |
| Sonnet 5 | $0.00011 | $0.00128 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
odoo-respond-bid 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 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.
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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/odoo-respond-bid
This command is a thin dispatcher. All phase logic, gates, skill invocations, output paths, and fallback rules are defined in the declarative workflow SSOT:
plugins/odoo-ai-agents/workflows/odoo-respond-bid.workflow.yaml
How to run
The workflow-chaining skill auto-discovers odoo-respond-bid.workflow.yaml and executes it
when this command fires. Dispatch happens via natural-language routing - the runner reads
the workflow YAML and drives each phase in sequence.
To invoke: type /odoo-respond-bid (optionally followed by a customer label, e.g.
/odoo-respond-bid Customer-A). The runner collects remaining inputs interactively at
Phase 0.
What the workflow produces
Six gated phases (Pipeline pattern):
| Phase | Skill dispatched | Gate |
|---|---|---|
| 0 - Parse + context check | inline | implicit |
| 1 - Discovery synthesis | odoo-discovery-summary |
approve / refine: [feedback] / cancel |
| 2 - Gap analysis | odoo-gap-analysis |
approve / refine: [feedback] / cancel |
| 3 - Capability proof | odoo-capability-proof |
approve / refine: [feedback] / cancel |
| 4 - Objection pre-empt | odoo-objection-handling |
approve / refine: [feedback] / cancel |
| 5 - Assemble proposal | inline | approve / refine: [feedback] / cancel |
| 6 - Output | inline (write file) | - |
Gate replies are the two declared sets only (${CLAUDE_PLUGIN_ROOT}/snippets/planning-gate-contract.md),
matching workflows/odoo-respond-bid.workflow.yaml line for line. yes is not a gate keyword. At
Phase 5, approve saves the proposal file and prints it for copy-paste.
Output lands in <ISOLATE_DIR>/bids/<customer_label>-<YYYY-MM-DD>.md (resolve <SHARE_DIR>/<ISOLATE_DIR>
once per ${CLAUDE_PLUGIN_ROOT}/snippets/state-root-resolution.md; substitute the captured
absolute path - never write the placeholder or a bare .odoo-ai/ into a Read/Write/Edit).
For full phase specifications, gate behavior, standalone fallback rules, hard rules
(abstract labels, no external writes before Gate 5, no email sending), and examples -
read workflows/odoo-respond-bid.workflow.yaml directly.
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 · 53 lines · 56 tokens per session scan A 65c45f2cd44d
odoo-respond-bid is a command published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 4d ago), licensed MIT. It adds 56 tokens to every session and 638 once invoked, about $0.0003 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 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.