Borrowing it
Nothing to install: this file belongs to chama-x/GroundRules. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/chama-x/GroundRules/master/.agents/skills/odoo-rl-rules/SKILL.mdgit clone --depth 1 https://github.com/chama-x/GroundRulesWrote 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/chama-x/groundrules/odoo-rl-rules)<a href="https://agentmods.dev/skills/chama-x/groundrules/odoo-rl-rules"><img src="https://agentmods.dev/badge/skills/chama-x/groundrules/odoo-rl-rules.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.00037 | $0.00297 |
| Opus 5 | $0.00018 | $0.00148 |
| Sonnet 5 | $0.00007 | $0.00059 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
odoo-rl-rules 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 3d 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.
What it actually says
Odoo CLI Constraints and RL Rules
You are acting as an enforcer of Odoo's strictest performance and structural rules.
1. Naming Conventions
- Custom modules must always start with the project prefix.
- Custom fields injected into base models must start with
x_to avoid future core conflicts, unless building an entirely new custom model.
2. ORM Performance Rules (No N+1)
- NEVER loop over recordsets to execute
write()orsearch(). - Always use batched operations. For example, instead of
for rec in records: rec.write({'state': 'done'}), userecords.write({'state': 'done'}). - When fetching relational data in loops, ensure records are pre-fetched or use
read_group.
3. Security (ir.model.access)
- Every new model MUST have a corresponding
ir.model.access.csventry. - Agents must refuse to create a model if they do not also define access rules.
4. Views and Inherits
- Always use
xpathaccurately when inheriting views. - Never overwrite a core view's architecture completely; only append or replace targeted nodes.
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.
- 3d ago First seen · 26 lines · 37 tokens per session scan A f17627e4bcca
odoo-rl-rules is a skill published in the GitHub repository chama-x/GroundRules (5 stars, last pushed 23d ago), licensed MIT. It adds 37 tokens to every session and 297 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
notion-tool
Notion integration tool for searching, reading, creating, and updating pages and databases via the API. Use when: editing Notion pages, adding database rows, or searching a workspace.
jvm-server-frameworks
CIEL's framework for Ktor servers, Exposed ORM, and database lifecycle management.
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices. Use when building APIs, services, or server-side functionality.
embeddings
Vector embeddings with HNSW indexing, sql.js persistence, and hyperbolic support. 75x faster with agentic-flow integration. Use when: semantic search, pattern matching, similarity queries, knowledge retrieval. Skip when: exact text matching, simple lookups, no semantic understanding needed.
platform-custom-field-generate
Use this skill when users need to create, generate, or validate Salesforce Custom Field metadata. Trigger when users mention custom fields, field types, Roll-up Summary fields, Master-Detail relationships, Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from…