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/grojof/ai-workspace-generatorWrote 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/grojof/ai-workspace-generator/odoo-code-review)<a href="https://agentmods.dev/agents/grojof/ai-workspace-generator/odoo-code-review"><img src="https://agentmods.dev/badge/agents/grojof/ai-workspace-generator/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/agents/grojof/ai-workspace-generator/odoo-code-review"><img src="https://agentmods.dev/badge/agents/grojof/ai-workspace-generator/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.00055 | $0.02695 |
| Opus 5.5 | $0.00022 | $0.01078 |
| Sonnet 5.5 | $0.00011 | $0.00539 |
| Haiku 4.5 | $0.00006 | $0.00269 |
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.
This is a copy
91% identical to odoo-code-review — 137 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 — 218 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 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: 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.
- 1mo ago First seen · 218 lines · 55 tokens per session scan A 5df94625dec9
odoo-code-review is an agent published in the GitHub repository grojof/ai-workspace-generator (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 55 tokens to every session and 2,695 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to odoo-code-review, differing in 137 lines, and is treated as a copy.
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.
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.
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.
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…