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-deprecation-audit)<a href="https://agentmods.dev/skills/viindoo/odoo-mcp-client/odoo-deprecation-audit"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-deprecation-audit/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-deprecation-audit"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-deprecation-audit.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.00246 | $0.03417 |
| Opus 5 | $0.00123 | $0.01708 |
| Sonnet 5 | $0.00049 | $0.00683 |
| Haiku 4.5 | $0.00025 | $0.00342 |
Grade A, and why
odoo-deprecation-audit 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 7d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Developer / Tech Lead
Out of Scope
- Version API diff without code scan → use
odoo-version-diff - Fresh code generation in target version → use
odoo-coding - Executive risk dashboard → use
odoo-risk-overview - General code correctness / security / performance review → route to
odoo-code-review
Reactive mode (dispatched by odoo-debug). When odoo-debug routes a deprecated-API-at-runtime symptom here (removed/changed symbol breaking after upgrade, with reproduction + two versions), root-cause THAT symptom following ${CLAUDE_PLUGIN_ROOT}/skills/_shared/debug-method.md and point at the replacement. A direct invocation stays a full pre-upgrade deprecation sweep.
Diff-scope mode (optional)
Default (no SCOPE_FILES/CHANGED_SET supplied): whole-module pre-upgrade sweep, UNCHANGED - a standalone invocation, and odoo-modules-upgrade/odoo-forward-port callers, are unaffected.
When a caller (e.g. agents/odoo-code-reviewer.md's ### Step 3.6 - Audit escalation) briefs this skill diff-scoped, it supplies:
SCOPE_FILES/CHANGED_SET- the diff's touched files. Restrict authoritative BREAKING/WARN/STYLE findings to those files plus their direct callers (blast-radius: reverse-dependency lookup, or a local grep for call-sites when OSM is unavailable). Report any finding outside that scope (pre-existing deprecated usage) in a separate "Pre-existing / blast-radius" section - never silently dropped.odoo_version(the source version) and, optionally,TARGET_SERIES(the upgrade target) - version-relative values the brief supplies; use them exactly as Round 0 / Round 1b already do. When absent, resolve the series per${CLAUDE_PLUGIN_ROOT}/snippets/project-facts-resolution.md. This skill never hardcodes a version number in its own prose - every version is a variable the ladder or the brief resolves.
Findings are graded on the shared scale defined in ${CLAUDE_PLUGIN_ROOT}/snippets/review-severity-rubric.md: this audit's own BREAKING/WARN/STYLE tiers map onto that scale's CRITICAL/HIGH/MED/LOW - one severity scale governs the whole review-plus-audit pipeline.
What ships with it
1 file 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.
- 7d ago First seen · 173 lines · 246 tokens per session scan A d09e3020e870
odoo-deprecation-audit is a skill published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 5d ago), licensed MIT. It adds 246 tokens to every session and 3,417 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-09-03.
Other skills, from other repositories
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
gsd-ns-review
Route to the appropriate quality / review skill based on the user's intent. gsd-code-review-fix was absorbed by gsd-code-review --fix in #2790.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…
gitnexus
A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.
cleanup-code-inspections
Reduce technical debt and improve code quality by systematically resolving static analysis warnings.
sonarqube-mcp
Provides SonarQube and SonarCloud integration patterns via the Model Context Protocol (MCP) server. Enables quality gate monitoring, issue discovery and triaging, pre-push code analysis, and rule education directly in the agent workflow. Use when the user wants to check quality gates, search for Sonar issues, analyze…