Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/MarioMillet2b/mcp-odooWrote 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/rules/mariomillet2b/mcp-odoo/odoo)<a href="https://agentmods.dev/rules/mariomillet2b/mcp-odoo/odoo"><img src="https://agentmods.dev/badge/rules/mariomillet2b/mcp-odoo/odoo.svg" alt="Measured on agentmods" 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.00014 | $0.00236 |
| Opus 5 | $0.00007 | $0.00118 |
| Sonnet 5 | $0.00003 | $0.00047 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
odoo 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 5d 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.
This is a copy
100% identical to odoo — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
- Before guessing any Odoo schema, call
get_model_fields(userelevance="top"on wide models) orinspect_model_relationships. - If a model name might be outdated (e.g.
account.invoice), check it withlookup_model_historyfirst. - Never call
unlink/write/createdirectly throughexecute_method— use the gated workflow:preview_write→validate_write→execute_approved_write. - When several Odoo instances are configured, pass the
instanceargument on every tool call; runlist_instancesto discover them. - Prefer
search_recordswith explicit field lists over full-record fetches; useaggregate_recordsfor counts and sums instead of reading rows and adding them up yourself. - When a call fails with a permission error, pass the error text to
diagnose_accessasobserved_errorinstead of retrying blindly.
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.
- 5d ago First seen · 20 lines · 14 tokens per session scan A 6128567e2e25
odoo is a cursor rule published in the GitHub repository MarioMillet2b/mcp-odoo (0 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 236 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to odoo, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.