odoo-development

Development rules for Odoo, a business application platform, covering Python modules, database models, XML views, access controls, reports, assets, and translations.

In plain words
What is it for?
Use it when creating or reviewing Odoo modules, naming models and classes, organizing files, and defining views, security rules, reports, or translations.
Why use it?
It helps keep Odoo modules in the directory layout and naming style expected by the platform.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/mart337i/odoo-dev-mcp/odoo-development
Clone the repo
git clone --depth 1 https://github.com/mart337i/odoo-dev-mcp
Per session 3,026 This file is loaded in full into every session.
When invoked 3,026 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.03026 $0.03026
Opus 5 $0.01513 $0.01513
Sonnet 5 $0.00605 $0.00605
Haiku 4.5 $0.00303 $0.00303

Measured 2d ago against content hash eaea145af701, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

odoo-development 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 2d 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.

rules/odoo-development.mdc · 451 lines

How it starts

The opening of the file, as written. The whole thing — 451 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Odoo Development Guidelines

Module Structure

Naming Conventions

  • Module names: Use lowercase with underscores (e.g., sale_extended, inventory_custom)
  • Technical name: Same as module directory name
  • Display name: Human-readable with spaces (e.g., "Sales Extended")
  • Never use hyphens in module names

Directory Structure

module_name/
├── __init__.py              # Import submodules
├── __manifest__.py          # Module metadata
├── models/                  # Python models
│   ├── __init__.py
│   └── model_name.py
├── views/                   # XML views
│   └── model_views.xml
├── security/                # Access rights and rules
│   ├── ir.model.access.csv
│   └── module_security.xml
├── data/                    # Data files
├── wizard/                  # Transient models
├── report/                  # Report definitions
├── static/                  # Static assets
│   ├── description/
│   │   └── icon.png        # 128x128 PNG
│   └── src/
└── i18n/                    # Translations

Python Coding Standards

Model Naming

  • Model name: Use dot notation (e.g., sale.order.line)
  • Class name: CamelCase matching model (e.g., SaleOrderLine)
  • Inherit: Use _inherit for extension, _inherits for delegation
  • Never use underscore in model names (use dots)

Field Naming

  • Field names: lowercase_with_underscores
  • Boolean fields: Start with is_, has_, or can_ (e.g., is_active)
  • Many2one fields: End with _id (e.g., partner_id)
  • One2many/Many2many fields: End with _ids (e.g., line_ids)
  • Computed fields: Descriptive names, add compute parameter

Field Types and Parameters

# Char fields
name = fields.Char(string='Name', required=True, index=True)

# Many2one with domain and context
partner_id = fields.Many2one(
    'res.partner',
    string='Customer',
    required=True,
    domain="[('customer_rank', '>', 0)]",
    context="{'default_customer_rank': 1}"
)

# Selection field
state = fields.Selection([
    ('draft', 'Draft'),
    ('confirmed', 'Confirmed'),
    ('done', 'Done'),
], string='Status', default='draft', required=True)

# Computed field
total_amount = fields.Float(
    string='Total',
    compute='_compute_total_amount',
    store=True
)

Read the full file on GitHub · 451 lines

Changes

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.

  1. 2d ago First seen · 451 lines · 3,026 tokens per session scan A eaea145af701

Subscribe to this mod's changes

odoo-development is a cursor rule published in the GitHub repository mart337i/odoo-dev-mcp (21 stars, last pushed 3mo ago), licensed MIT. It adds 3,026 tokens to every session, about $0.0151 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-30.