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-run-brl)<a href="https://agentmods.dev/commands/viindoo/odoo-mcp-client/odoo-run-brl"><img src="https://agentmods.dev/badge/commands/viindoo/odoo-mcp-client/odoo-run-brl/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-run-brl"><img src="https://agentmods.dev/badge/commands/viindoo/odoo-mcp-client/odoo-run-brl.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.00097 | $0.01415 |
| Opus 5 | $0.00048 | $0.00707 |
| Sonnet 5 | $0.00019 | $0.00283 |
| Haiku 4.5 | $0.00010 | $0.00142 |
Grade A, and why
odoo-run-brl 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/odoo-run-brl
Thin dispatcher for the odoo-brl skill. Accepts an optional $ARGUMENTS token for
the customer label (e.g. /odoo-run-brl Customer-A). All orchestration logic lives in the
skill body - this command is a recipe shim only, following the 1-orchestration-SSOT rule.
Named
odoo-run-brl(notodoo-brl) so the command name stays disjoint from the skill name. The skill also auto-registers/odoo-ai-agents:odoo-brl; this command is the convenience entry point taking a customer-label argument and dispatching to the same skill body - one orchestration mechanism, two entry points.
When to use
Type /odoo-run-brl when you have a list of business requirements (tens to thousands of items)
and need:
- 4-way classification per item (Available-in-Odoo-CE / -EE / Available-in-Viindoo / Custom)
- Deterministic cost estimate (lookup table from
cost-config.json, auditable for client proposals) - RTM export (rtm.csv for Excel, results.jsonl for machine consumption)
- Executive report (report.md with classification mix, budget range, risk flags)
For a single feature check: use /odoo-ai-agents:odoo-feature-check instead.
For a short ad-hoc gap matrix (no cost, no scale): use /odoo-ai-agents:odoo-gap-analysis instead.
Hard rules
- Phase gate mandatory. GATE 0 blocks all classification work; GATE E blocks all deliverable writes. The command does NOT advance past either gate without explicit user confirmation.
- Project facts. At startup, resolve the Odoo series and OSM profile by working the rungs of
${CLAUDE_PLUGIN_ROOT}/snippets/project-facts-resolution.mdin order, stopping at the first that answers; ask only for what every rung left unresolved. When no[[instance]]covers this repo, offer/odoo-ai-agents:odoo-setupto declare one - an offer, never a precondition. Resolve<SHARE_DIR>/<ISOLATE_DIR>once per${CLAUDE_PLUGIN_ROOT}/snippets/state-root-resolution.mdbefore any state-root read or write; substitute the captured absolute path - never write the placeholder or a bare.odoo-ai/into a Read/Write/Edit. - Abstract labels. Use the customer label from
$ARGUMENTSor default "Customer-A". Never write real company names, VND figures, or internal pricing into any committed file. - Dispatch via the Skill tool. This command fires the
odoo-brlskill using the Skill tool. NL description-match is the fallback when the Skill tool is unavailable. - Public repo safety. All job artifacts go to
<SHARE_DIR>/brl/<job-id>/which is gitignored. No deliverable is committed to the repo.
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 · 105 lines · 97 tokens per session scan A 5dcf5a93572a
odoo-run-brl is a command published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 4d ago), licensed MIT. It adds 97 tokens to every session and 1,415 once invoked, about $0.0005 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.