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.
npx skills add unclecatvn/agent-skills --skill odoo-code-reviewgit clone --depth 1 https://github.com/unclecatvn/agent-skillsWrote 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/unclecatvn/agent-skills/odoo-code-review)<a href="https://agentmods.dev/skills/unclecatvn/agent-skills/odoo-code-review"><img src="https://agentmods.dev/badge/skills/unclecatvn/agent-skills/odoo-code-review.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00058 | $0.02872 |
| Opus 5 | $0.00029 | $0.01436 |
| Sonnet 5 | $0.00012 | $0.00574 |
| Haiku 4.5 | $0.00006 | $0.00287 |
Grade A, and why
odoo-code-review 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Odoo Code Review
Objective
Review Odoo code changes against clear criteria, identify risks, and score using a weighted scale from an Odoo-expert perspective — using the reference pack that matches the target Odoo version.
Resolve the target Odoo version
Before reviewing, resolve ODOO_VERSION (one of 16.0, 17.0, 18.0, 19.0) in this order. Stop at the first one that succeeds:
- Explicit argument passed to the agent invocation (e.g.
odoo_version: "19.0"). - Project config, in this order:
.odoo-versionfile at the repo root (contents: e.g.19.0).odoo_versionkey in.claude/odoo.json.odoo.versionkey inpackage.jsonortool.odoo.versioninpyproject.toml.
- Manifest heuristic — scan workspace
__manifest__.pyfiles for the'version'key. Use the dominant major version (e.g.18.0.1.0.0→18.0). - Fallback — default to
19.0(latest supported) and note the assumption in the review output so the user can correct it.
Derive ODOO_MAJOR from ODOO_VERSION by stripping .0 (e.g. 18.0 → 18). All guide paths below use these placeholders.
Supported versions: 16.0, 17.0, 18.0, 19.0. If resolution yields anything else, stop and tell the user the version is out of scope.
Pre-review Requirements
- Read
skills/odoo-${ODOO_VERSION}/SKILL.mdas the master index for the resolved version's guides. - Read
skills/odoo-${ODOO_VERSION}/references/api-highlights.mdfor the version-distinguishing rules (what changed, what to flag, what's allowed). - Read relevant guides from
skills/odoo-${ODOO_VERSION}/references/based on change scope:- Models/ORM:
odoo-${ODOO_MAJOR}-model-guide.md - Fields:
odoo-${ODOO_MAJOR}-field-guide.md - Decorators:
odoo-${ODOO_MAJOR}-decorator-guide.md - Performance:
odoo-${ODOO_MAJOR}-performance-guide.md - Views/XML:
odoo-${ODOO_MAJOR}-view-guide.md - Security:
odoo-${ODOO_MAJOR}-security-guide.md - Controllers:
odoo-${ODOO_MAJOR}-controller-guide.md - Transactions:
odoo-${ODOO_MAJOR}-transaction-guide.md - Mixins:
odoo-${ODOO_MAJOR}-mixins-guide.md(mail.thread, activities) - Testing:
odoo-${ODOO_MAJOR}-testing-guide.md - Migration:
odoo-${ODOO_MAJOR}-migration-guide.md - Actions:
odoo-${ODOO_MAJOR}-actions-guide.md - Data Files:
odoo-${ODOO_MAJOR}-data-guide.md - Manifest:
odoo-${ODOO_MAJOR}-manifest-guide.md
- Models/ORM:
- Identify scope: module, file, and change context.
- Apply the version-distinguishing rules from
api-highlights.md(e.g.<tree>vs<list>,group_operator=vsaggregator=, optional_namein v19, etc.).
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.
- 8d ago First seen · 230 lines · 58 tokens per session scan A 5d2e64712fae
odoo-code-review is a skill published in the GitHub repository unclecatvn/agent-skills (130 stars, last pushed 15d ago), licensed MIT. It adds 58 tokens to every session and 2,872 once invoked, about $0.0003 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.
Other skills, from other repositories
platform-apex-generate
Primary Apex authoring skill for class generation, refactoring, and review. ALWAYS ACTIVATE when the user mentions Apex, .cls, triggers, or asks to create/refactor a class (service, selector, domain, batch, queueable, schedulable, invocable, DTO, utility, interface, abstract, exception, REST resource). Use this skill…
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
api-contract-review
Use when auditing CloudBase cloud API wrappers, MCP tools, generated action metadata, or related docs for outdated or incorrect action names, parameters, casing, request shapes, or missing contract tests, especially during periodic quality review or before preparing corrective PRs.
principle-model-the-domain
Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files. Encode the domain in a structure instead of scattered conditionals.
code-review-nodejs
Applies Node.js-specific code review patterns for async I/O, streams, security, process management, and dependency hygiene. Use when reviewing Node.js server code, route handlers, middleware, or any JavaScript file alongside package.json without TypeScript. Triggers on sync I/O in request paths, missing stream…