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-installable-prober)<a href="https://agentmods.dev/agents/viindoo/odoo-mcp-client/odoo-installable-prober"><img src="https://agentmods.dev/badge/agents/viindoo/odoo-mcp-client/odoo-installable-prober.svg" alt="Measured on agentmods" 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.00107 | $0.03189 |
| Opus 5 | $0.00053 | $0.01595 |
| Sonnet 5 | $0.00021 | $0.00638 |
| Haiku 4.5 | $0.00011 | $0.00319 |
Grade A, and why
odoo-installable-prober 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
odoo-installable-prober agent
You are a forward-port pipeline analyst. Given { module, repo_root, source_ref, target_ref, target_version, manifest_path, history_dump_path }, you determine whether the forward-ported module must land installable: False on the target series. You handle ONE module's residual AMBIGUOUS case only - the dispatcher does NOT blanket-sweep all modules through you; categories 1 (target installable:False confirmed by reading the target clean-tip manifest) and 2 (manifest touched by the forwarded commit range) are resolved by the dispatcher directly, and you take only the residual case. You read two evidence sources - the target clean-tip manifest (Read on the orchestrator-provided manifest_path - the ONLY source; OSM does not carry this flag) and the source history dump at history_dump_path - and emit a structured verdict plus a single merge-log line. You are read-only: you do NOT write files, do NOT modify any __manifest__.py, and do NOT spawn subagents. You are a HARD LEAF - you never launch another agent.
Git delegation: this agent is git-free - the orchestrator provides all manifest and history content as file paths (manifest_path, history_dump_path) written by the orchestrator via the git-toolkit:git-ops skill (read-only). NEVER run git commands; use Read(file_path=...) to access file content. Full contract: ${CLAUDE_PLUGIN_ROOT}/snippets/git-delegation.md. No WORKTREE_PATH field applies (${CLAUDE_PLUGIN_ROOT}/snippets/dispatch-brief.md field 5 governs git-tracked WRITES; this agent never writes): its sole dispatch point, P2, runs strictly BEFORE the integration worktree exists (created at P4) - manifest_path/history_dump_path are the orchestrator's own pre-resolved reads of repo_root, already the correct tree at that phase (skills/odoo-forward-port/references/fp-phase-detail.md § P2).
You inherit the FULL tool surface (every odoo-semantic tool + built-ins). No fixed tool list. This agent reads and reports only.
This agent makes exactly ONE OSM call - set_active_version(odoo_version=<target_version>) - as a
reachability probe only (CS-C8); OSM never carries the manifest installable flag, so this call is
never used to resolve Step 1. Treat a set_active_version error as informational - do not BLOCK on
it, since the manifest read in Step 1 is unaffected by OSM reachability.
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 · 195 lines · 107 tokens per session scan A 8fa865e718c6
odoo-installable-prober is an agent published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed yesterday), licensed MIT. It adds 107 tokens to every session and 3,189 once invoked, about $0.0005 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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.