Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/ahmed-lakosha/odoo-pluginsWrote 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/commands/ahmed-lakosha/odoo-plugins/odoo-precheck)<a href="https://agentmods.dev/commands/ahmed-lakosha/odoo-plugins/odoo-precheck"><img src="https://agentmods.dev/badge/commands/ahmed-lakosha/odoo-plugins/odoo-precheck/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/commands/ahmed-lakosha/odoo-plugins/odoo-precheck"><img src="https://agentmods.dev/badge/commands/ahmed-lakosha/odoo-plugins/odoo-precheck.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.00016 | $0.00279 |
| Opus 5 | $0.00008 | $0.00139 |
| Sonnet 5 | $0.00003 | $0.00056 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
odoo-precheck 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 10d 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.
What it actually says
Perform a read-only compatibility scan on the Odoo module at: $ARGUMENTS
DO NOT modify any files. Only read and report.
Scan all files in the module for:
- XML:
<tree>tags,<group>in search views,kanban-boxtemplates,numbercallfields,active_idin contexts,//treeXPaths,website.snippet_optionsinheritance - Python:
openerpimports,type='json'in routes,treein view_mode, deprecated slug/url_for imports - JavaScript:
useService("rpc"),@web/core/network/rpc_serviceimports, OWL 1.x lifecycle methods - SCSS: deprecated variable names (
$headings-font-weightetc.)
Report all issues grouped by severity:
- CRITICAL: Will cause installation to fail
- HIGH: Will likely cause runtime errors
- MEDIUM: Should fix for full compatibility
- LOW: Minor, optional improvements
For each issue, show the file path, line number, and a brief description of what needs to change.
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.
- 10d ago First seen · 23 lines · 16 tokens per session scan A 40b60800dc70
odoo-precheck is a command published in the GitHub repository ahmed-lakosha/odoo-plugins (74 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 279 once invoked, about $0.0001 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-30.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.