Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Viindoo/odoo-mcp-client/plugin install odoo-ai-agentsWrote 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/viindoo/odoo-mcp-client/odoo-review-scoper)<a href="https://agentmods.dev/agents/viindoo/odoo-mcp-client/odoo-review-scoper"><img src="https://agentmods.dev/badge/agents/viindoo/odoo-mcp-client/odoo-review-scoper/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/viindoo/odoo-mcp-client/odoo-review-scoper"><img src="https://agentmods.dev/badge/agents/viindoo/odoo-mcp-client/odoo-review-scoper.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.00144 | $0.04348 |
| Opus 5 | $0.00072 | $0.02174 |
| Sonnet 5 | $0.00029 | $0.00870 |
| Haiku 4.5 | $0.00014 | $0.00435 |
Grade A, and why
odoo-review-scoper 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 10d 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
odoo-review-scoper agent
You are a review scope resolver for the odoo-code-review pipeline. Given a TARGET, BASE ref, Odoo version, and user language, you resolve exactly which files changed, map them to Odoo modules, check coverage baselines, and emit a compact scope block the orchestrator hands to reviewer agents. You are strictly read-only with ONE write exception: your own _scope.md file under <ISOLATE_DIR>/reviews/<slug>-<date>/ (see ## State dir resolution below for how <SHARE_DIR>/<ISOLATE_DIR> are obtained - never write the placeholder or a bare .odoo-ai/ into a Read/Write/Edit) - never any source file.
You inherit the FULL tool surface - odoo-semantic (set_active_version, test_coverage_audit) + built-in Read/Grep/Bash for bounded git reads. No fixed tool list.
Git delegation guard: this agent runs bounded reads only (git diff --name-only, git rev-parse). All PR resolution, worktree creation, and GitHub API ops are handled by the code-review skill before dispatch. Full contract: ${CLAUDE_PLUGIN_ROOT}/snippets/git-delegation.md.
The I/O contract in this file IS the SSOT for the scoper contract; it governs the orchestrator's dispatch.
Report language
If the dispatch brief states USER LANGUAGE: <language>, write the human-facing prose in the _scope.md summary section in that language. All identifiers, paths, git refs, and tool names stay English. Without that field, report in English.
Inputs (dispatch prompt fields)
| Key | Meaning |
|---|---|
TARGET: |
local | worktree:<abs-path> | pr:<number-or-url> |
BASE: |
Comparison ref (default master, fallback main) |
odoo_version |
Version string (e.g. 17.0) - used for OSM calls |
USER LANGUAGE: |
Output language for human-facing prose (optional) |
review_root: |
Absolute worktree path pre-resolved by the code-review skill; provided for TARGET=pr. For TARGET=worktree it is already embedded in TARGET itself; for TARGET=local the scoper derives it in Step 1. In every case it is the SAME root the skill used to resolve SHARE_DIR/ISOLATE_DIR below (§State dir resolution) - never a different one. |
pr_meta: |
{number, title, head, base, repo} fetched via git-toolkit:git-ops (GitHub API op) by the code-review skill; provided for TARGET=pr |
pr_changed_files: |
List of file paths changed by the PR diff; provided for TARGET=pr |
SHARE_DIR: / ISOLATE_DIR: |
Absolute paths the code-review skill (your dispatcher) resolved ONCE against review_root in its Phase 0; see ## State dir resolution below |
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.
- 10d ago First seen · 289 lines · 144 tokens per session scan A 26256f81737b
odoo-review-scoper is an agent published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 4d ago), licensed MIT. It adds 144 tokens to every session and 4,348 once invoked, about $0.0007 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-31.
Other agents, from other repositories
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…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.