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-deploy-checklist)<a href="https://agentmods.dev/skills/viindoo/odoo-mcp-client/odoo-deploy-checklist"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-deploy-checklist/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-deploy-checklist"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-deploy-checklist.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.00231 | $0.02032 |
| Opus 5 | $0.00115 | $0.01016 |
| Sonnet 5 | $0.00046 | $0.00406 |
| Haiku 4.5 | $0.00023 | $0.00203 |
Grade A, and why
odoo-deploy-checklist 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 6d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Engineer / DevOps - Odoo developer or sysadmin on a one-man-company team or small team preparing a production or staging release. Audience may range from solo Odoo consultant to a 3-5 person dev shop. Output is operational and actionable, not executive-level.
Out of Scope
| Topic | Skill to use instead |
|---|---|
| Deprecated API code audit (pre-upgrade code scan) | odoo-deprecation-audit |
| API + feature diff between two Odoo versions | odoo-version-diff |
| Full upgrade orchestration plan (multi-tool) | /odoo-plan-upgrade (Phase C command) |
| Executive risk dashboard for stakeholders | odoo-risk-overview |
| Backend coding fixes found during checklist | odoo-coding bundle |
MCP tools
Session bootstrap (optional - call once if version not already pinned):
set_active_version(odoo_version='<version>')- Pin a CONCRETE Odoo version (sentinels like 'auto' are rejected; the call doubles as a cheap reachability probe; 24h idle TTL).
Primary tools:
check_module_exists- Verify that each module in the deploy scope actually exists in the target Odoo version. Use in Round 2 to auto-fill module existence items.module_inspect- Get module manifest summary, model list, view count, and OWL component presence for deploy notes. Use to confirm module health and spot unexpected dependencies.find_deprecated_usage- Sanity scan for deprecated API usage in deploy scope. Supplementsodoo-deprecation-auditwhen a full pre-flight audit was not run separately.cli_help- Ground the deploy/test CLI flags (--test-enable,--test-tags,-u,-i,--stop-after-init) for the TARGET version in Domain 5, instead of assuming one version's flags apply to another.
The module-scan calls are independent - fire in parallel to minimize round trips.
Checklist domains
Eight standard domains - every deploy checklist covers all eight. Items are auto-filled where context is available; remaining items flagged for manual verification.
What ships with it
2 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.
- 6d ago First seen · 146 lines · 231 tokens per session scan A 08e10029c49d
odoo-deploy-checklist is a skill published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 3d ago), licensed MIT. It adds 231 tokens to every session and 2,032 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
migrate-vstest-to-mtp
Use this skill before answering, planning, or editing whenever .NET tests or CI are switching from VSTest to Microsoft.Testing.Platform (MTP), or an MTP migration behaves differently. Triggers include "switch from VSTest"; MSTest/NUnit/xUnit MTP enablement; OutputType=Exe only for test projects in…
ci
Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
playwright-testing
E2E testing with Playwright - Page Objects, cross-browser, CI/CD.
ci-maintenance-workflow
CI and GitHub Actions maintenance workflows — fix a failing test from a CI URL, fix a failing smoke test, add @pytest.mark.slow markers to slow tests, or review a PR against agent-checkable standards. Use when user asks to fix a failing test, fix a smoke test, mark slow tests, or review a PR. Trigger when the user…
test-setup
Scaffold the test framework and CI/CD pipeline for the project's engine. Creates the tests/ directory structure, engine-specific test runner configuration, and GitHub Actions workflow. Run once during Technical Setup phase before the first sprint begins.