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/skills/viindoo/odoo-mcp-client/odoo-deep-survey)<a href="https://agentmods.dev/skills/viindoo/odoo-mcp-client/odoo-deep-survey"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-deep-survey/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/viindoo/odoo-mcp-client/odoo-deep-survey"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-deep-survey.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.00230 | $0.06063 |
| Opus 5 | $0.00115 | $0.03031 |
| Sonnet 5 | $0.00046 | $0.01213 |
| Haiku 4.5 | $0.00023 | $0.00606 |
Grade A, and why
odoo-deep-survey 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 11d 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 — 363 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Odoo Deep Survey - broad→narrow→deep, then synthesize
Consumer: the next execute AI agent (architect, coder, reviewer) - not a human. Every
finding must be actionable without re-derivation: a file:line pointer or OSM citation, marked
RESOLVED or UNRESOLVED, written so a downstream agent reads few tokens and understands at once.
Role
Read-only reconnaissance orchestrator. Loaded by the Skill tool from the main context, it
fans out anonymous worker agents to map "can the codebase actually meet this intent, and where
does the work land?" - at three escalating tiers of cost and depth. Writes analysis artifacts
under <SHARE_DIR>/survey/ (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 writes Odoo source.
When this runs (opt-in only)
odoo-intake emits a Proposed Plan from a light Phase R recon, then offers a deep survey. The
user replies refine: deep-survey at that plan gate - the PLAN reply set
(${CLAUDE_PLUGIN_ROOT}/snippets/planning-gate-contract.md); deep-survey is the feedback, not a
gate keyword of its own. ONLY THEN does intake invoke this skill via the Skill tool. This is
the human gate - this skill produces no routed deliverable, only analysis that re-informs the
plan. It is heavy (many subagents, real tokens), which is why it is opt-in and never automatic.
Inputs (passed by intake in the invocation)
- Intent / purpose / expected outcomes - the closed Phase 0 gate (what / why / done-looks-like).
- Odoo series + profile - from the intake version gate, else resolved per
${CLAUDE_PLUGIN_ROOT}/snippets/project-facts-resolution.md. Pin this concrete series on every OSM call (see § OSM grounding). - The first Proposed Plan - so synthesis can express its findings as a delta against it.
- Slug - reuse the feature slug intake already uses for brainstorm artifacts; the survey dir
is
<SHARE_DIR>/survey/<slug>-<date>/.
What ships with it
3 files 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.
- 11d ago First seen · 363 lines · 230 tokens per session scan A 09b2411d6ada
odoo-deep-survey is a skill published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 4d ago), licensed MIT. It adds 230 tokens to every session and 6,063 once invoked, about $0.0011 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…