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/archive/v3/skill_odoo-discipline/skills/odoo-code-review/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-code-review)<a href="https://agentmods.dev/skills/chama-x/groundrules/odoo-code-review"><img src="https://agentmods.dev/badge/skills/chama-x/groundrules/odoo-code-review/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/skills/chama-x/groundrules/odoo-code-review"><img src="https://agentmods.dev/badge/skills/chama-x/groundrules/odoo-code-review.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.00075 | $0.01495 |
| Opus 5.5 | $0.00030 | $0.00598 |
| Sonnet 5.5 | $0.00015 | $0.00299 |
| Haiku 4.5 | $0.00007 | $0.00150 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Odoo Code Review
Use this skill for Odoo-specific code review. Findings come first. Focus on bugs, security risks, behavioral regressions, performance problems, migration hazards, and missing tests before style cleanup.
Official Odoo coding guidelines are still covered by ODOO-CODING-GUIDELINES.md, but review scope is broader than style.
First Move
Identify:
- target Odoo version
- addon/module scope
- changed files or diff range
- stable branch vs development branch
- repo-specific conventions and checks
- available local framework/tooling context:
$ODOO_SOURCE,$ODOO_TOOL_README,$ODOO_BASE_COMMAND
If a version-specific reference skill exists, consult it before reviewing version-sensitive behavior:
- Odoo 17:
odoo-17.0 - Odoo 18:
odoo-18.0 - Odoo 19:
odoo-19.0
If $ODOO_SOURCE is set, inspect local framework code for APIs, XML syntax, assets, test helpers, and version-specific behavior before relying on memory.
Review Workflow
- Determine the review target: whole addon, diff, PR, commit range, or specific files.
- Read the module manifest first, then relevant imports, models, views, security, data, controllers, tests, assets, reports, and docs.
- Check official style/guideline concerns with ODOO-CODING-GUIDELINES.md.
- Check Odoo behavior risks with the review checklist below.
- Return findings ordered by severity with file/line references.
- State checks run, checks not run, and residual review gaps.
Stable Branch Rule
When reviewing stable branches, do not ask for noisy restyling. Existing file style supersedes generic formatting preferences. Focus on changed code, correctness, security, maintainability, and obvious guideline violations.
In development branches, apply guidelines more broadly to modified code. Recommend restructuring only when it reduces real risk or the user asks for a wider cleanup.
Odoo Review Checklist
Models And ORM
- Model names,
_inherit, and_inheritsmatch real domain boundaries. - Batch operations are used for multi-record flows.
- No
search(),browse(),create(),write(), orunlink()inside loops unless bounded and justified. - Domains are correct, indexed where relevant, and multi-company-safe.
sudo()is used only at explicit trust boundaries and does not leak records.- Direct SQL is parameterized and justified.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 145 lines · 75 tokens per session scan A 33a2a9dcf0aa
odoo-code-review is a skill published in the GitHub repository chama-x/GroundRules (5 stars, last pushed 2mo ago), licensed MIT. It adds 75 tokens to every session and 1,495 once invoked, about $0.0003 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-31.
Other skills, from other repositories
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
agent-reviewer
Agent skill for reviewer - invoke with $agent-reviewer.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…
github
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available)…
write-skills
Create or revise agent skills. Use when adding a new skill file, renaming a skill, simplifying an existing skill, improving trigger descriptions, or deciding what belongs in a skill versus references, scripts, assets, or ordinary docs.