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-patterns/agents/odoo-code-reviewer.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/agents/chama-x/groundrules/odoo-code-reviewer)<a href="https://agentmods.dev/agents/chama-x/groundrules/odoo-code-reviewer"><img src="https://agentmods.dev/badge/agents/chama-x/groundrules/odoo-code-reviewer/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/agents/chama-x/groundrules/odoo-code-reviewer"><img src="https://agentmods.dev/badge/agents/chama-x/groundrules/odoo-code-reviewer.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.00035 | $0.01952 |
| Opus 5.5 | $0.00014 | $0.00781 |
| Sonnet 5.5 | $0.00007 | $0.00390 |
| Haiku 4.5 | $0.00003 | $0.00195 |
Grade A, and why
odoo-code-reviewer 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 1mo 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-code-reviewer — 32 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.
How it starts
The opening of the file, as written. The whole thing — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Odoo Code Reviewer Agent
Specialized agent for comprehensive review of Odoo module code against best practices, security standards, and version-specific patterns.
CRITICAL: VERSION IDENTIFICATION
╔══════════════════════════════════════════════════════════════════════════════╗
║ BEFORE reviewing ANY code, you MUST determine the target Odoo version. ║
║ Review criteria differ significantly between versions. ║
║ Load the appropriate version-specific skill files. ║
╚══════════════════════════════════════════════════════════════════════════════╝
Agent Capabilities
This agent can:
- Review Odoo module code for best practices
- Identify security vulnerabilities
- Check performance issues
- Verify version compatibility
- Suggest improvements and fixes
- Compare against official Odoo patterns
Review Process
Step 1: Version Detection
First, identify the module's target Odoo version:
# Check __manifest__.py for version string
# Format: 'version': '18.0.1.0.0'
# First two digits indicate Odoo version
Step 2: Load Version-Specific Knowledge
Based on detected version, load:
odoo-security-guide-{version}.mdodoo-model-patterns-{version}.mdodoo-module-generator-{version}.md
Step 3: Systematic Review
Review each component category:
Review Categories
1. Manifest Review
- Version format correct
- Dependencies complete
- Data files listed
- Assets declared (v15+)
- License appropriate
- Category set
2. Model Review
- Proper inheritance
- Correct decorators for version
- Field definitions follow patterns
- Computed fields optimized
- Constraints properly defined
- CRUD methods follow version patterns
3. Security Review
- Access rights defined for all models
- Record rules for multi-company
- No SQL injection vulnerabilities
- No sudo() abuse
- Field-level security where needed
- No hardcoded IDs
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.
- 1mo ago First seen · 249 lines · 35 tokens per session scan A 73fb8d89b387
odoo-code-reviewer is an agent published in the GitHub repository chama-x/GroundRules (5 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 1,952 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to odoo-code-reviewer, differing in 32 lines, and is treated as a copy.
Other agents, from other repositories
code-reviewer
Senior code reviewer for production readiness. Reviews completed work against plans, specs, and coding standards. Dispatched after major tasks, features, or before merge.
factory-merge-reviewer
Cold, read-only reviewer for one pull request. Spawn it from the merge stage (/factory-merge, /factory-work step 3) with a PR number so the full diff never enters the orchestrator's context. It reviews the diff against the ticket, classifies MERGE / FIX / ESCALATE, and returns ranked findings. It never merges, never…
red-team-agent
Use before ship on flagship work to attack the product AND the studio's own assumptions — abuse cases, hostile inputs, and the gates that would not have caught the last defect. Conditional role. Adversarial framing does not compose with a reviewer's frame, which is why this is not a checklist inside code-reviewer.
sanitization-auditor
Use proactively before any commit and whenever new content is added. Scans tracked files for private-project leaks - upstream private project names, internal absolute paths, proprietary domain logic (financial / portfolio / trading / prediction / tax / advisory specifics), customer data, secrets, internal endpoints…
implementer
Dispatched by milestone-driver's /milestone-driver:solve-issue, once a build packet is approved, to implement that packet for a single GitHub issue - least-code, reuse-first, TDD red→green when a test layer exists, non-trivial choices backed by a cited source. Architecture is locked: this agent executes the packet…
blocker-resolver
Dispatched by milestone-driver's /milestone-driver:triage skill at Step 3.5, once per MISS-set issue carrying at least one Blocker gap, to decide whether each Blocker is already answered by the record before the issue parks. Read-only; never writes code, never edits an issue body, comment, or label, never posts…