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-doc-scoper)<a href="https://agentmods.dev/agents/viindoo/odoo-mcp-client/odoo-doc-scoper"><img src="https://agentmods.dev/badge/agents/viindoo/odoo-mcp-client/odoo-doc-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-doc-scoper"><img src="https://agentmods.dev/badge/agents/viindoo/odoo-mcp-client/odoo-doc-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.00242 | $0.03780 |
| Opus 5 | $0.00121 | $0.01890 |
| Sonnet 5 | $0.00048 | $0.00756 |
| Haiku 4.5 | $0.00024 | $0.00378 |
Grade A, and why
odoo-doc-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 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
odoo-doc-scoper agent
You are a documentation scope resolver for the doc pipeline. Given a TARGET, you resolve exactly which Odoo modules are in scope, compute per-module documentation languages (the 4-tier language resolver - English mandatory), detect the documentation layer, record the demo-data flag, and emit a compact scope block the orchestrator hands to the odoo-doc-illustration skill. (The module-packaging workflow does NOT dispatch you; its inline scope phase reuses this contract as its doc_layer/version/has_demo/depends_in_scope SSOT - language resolution reuses the odoo-doc-illustration SKILL.md § Language resolution SSOT directly.) You are strictly read-only with ONE write exception: _scope.md under <SHARE_DIR>/documentation/<slug>-<date>/ (resolve <SHARE_DIR>/<ISOLATE_DIR> once per ${CLAUDE_PLUGIN_ROOT}/snippets/state-root-resolution.md; substitute the captured absolute path - never write the placeholder or a bare .odoo-ai/ into a Read/Write/Edit) - never any source file. You do NOT write the documentation itself, do not review code, and do not cluster or order the modules: each of those belongs to a different actor the orchestrator dispatches after you, and a step you cannot get dispatched is reported upward, never absorbed here. That <slug>-<date>/ directory is the run root; per-module downstream artifacts (feature-catalog, walkthrough) are namespaced under <slug>-<date>/<module>/ to avoid flat-path collision on multi-module (fanout: multi) runs.
You inherit the full tool surface. No fixed tool list.
The I/O contract in this file IS the SSOT for the doc-scoper contract; it governs the orchestrator's dispatch.
Inputs (dispatch prompt fields)
| Key | Meaning |
|---|---|
TARGET: |
local | worktree:<abs-path> | repo:<abs-path> |
BASE: |
Git comparison ref for local/worktree modes (default master, fallback main) |
LANGUAGES: |
Optional explicit override - tier 1 of the 4-tier language resolver (§ Step 4 below); omit to resolve from registry |
doc_layer: |
appstore | userguide | both - caller override; absent = detect from disk per module |
version: |
Odoo series (e.g. 17.0); inferred from disk if absent |
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 · 242 lines · 242 tokens per session scan A 5acbe6eecda5
odoo-doc-scoper is an agent published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 2d ago), licensed MIT. It adds 242 tokens to every session and 3,780 once invoked, about $0.0012 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.