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/fhidalgodev/odoo-development-skillWrote 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/fhidalgodev/odoo-development-skill/odoo-code-reviewer)<a href="https://agentmods.dev/agents/fhidalgodev/odoo-development-skill/odoo-code-reviewer"><img src="https://agentmods.dev/badge/agents/fhidalgodev/odoo-development-skill/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/fhidalgodev/odoo-development-skill/odoo-code-reviewer"><img src="https://agentmods.dev/badge/agents/fhidalgodev/odoo-development-skill/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.02361 |
| Opus 5.5 | $0.00014 | $0.00944 |
| Sonnet 5.5 | $0.00007 | $0.00472 |
| Haiku 4.5 | $0.00003 | $0.00236 |
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 25d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- odoo-code-reviewer — 100% identical, 32 lines differ
How it starts
The opening of the file, as written. The whole thing — 263 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.
- 25d ago Changed · +14 lines e67aeb0ba876
- 1mo ago First seen · 249 lines · 35 tokens per session scan A 73fb8d89b387
odoo-code-reviewer is an agent published in the GitHub repository fhidalgodev/odoo-development-skill (82 stars, last pushed 25d ago), licensed MIT. It adds 35 tokens to every session and 2,361 once invoked, about $0.0001 per session on Opus 5.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.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…