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.
npx skills add erpipe-org/mcp-odoo --skill odoo-data-quality-gategit clone --depth 1 https://github.com/erpipe-org/mcp-odooWrote 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/erpipe-org/mcp-odoo/odoo-data-quality-gate)<a href="https://agentmods.dev/skills/erpipe-org/mcp-odoo/odoo-data-quality-gate"><img src="https://agentmods.dev/badge/skills/erpipe-org/mcp-odoo/odoo-data-quality-gate/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/erpipe-org/mcp-odoo/odoo-data-quality-gate"><img src="https://agentmods.dev/badge/skills/erpipe-org/mcp-odoo/odoo-data-quality-gate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 57 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00085 | $0.00714 |
| Opus 5 | $0.00043 | $0.00357 |
| Sonnet 5 | $0.00017 | $0.00143 |
| Haiku 4.5 | $0.00009 | $0.00071 |
Grade A, and why
odoo-data-quality-gate 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- odoo-data-quality-gate — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Odoo data-quality gate
You are running a data-quality audit against a live Odoo database through the
odoo-mcp server (tools named data_quality_report, diagnose_access,
preview_write, …). Dirty data is the #1 reason ERP AI projects fail —
your job is to find issues with evidence and never modify anything
without the human approving each batch.
Prerequisites
- odoo-mcp connected (any Odoo 16+; check with
health_check). - Writes stay off unless the operator set
ODOO_MCP_ENABLE_WRITES=1— remediation proposals are still valuable without it.
Playbook
- Scope with the human. Which models matter? Default set for a general
audit:
res.partner,product.template,account.move. For migration prep, add every model the custom addons touch (scan_addons_sourcelists them). - Run the report per model:
data_quality_report(model=...). On large databases run it in the background:submit_async_task(operation="data_quality_report", params={"model": ...})then pollget_async_task. - Read
summary.checks_with_issuesand show evidence. Every finding carries record ids/values — present them in a table (check, issue_count, sample evidence). Never summarize away the ids; the human needs them. - Verify orphans before judging.
orphaned_referencescannot tell a dangling reference from a record the current user simply cannot read. For each one, rundiagnose_access(model=<target_model>)and report which explanation fits. - Propose remediation as batches, not actions. Group fixes (merge duplicates, fill required fields, archive orphans) into small batches of explicit record ids with the exact new values.
- Execute only through the gate, one approved batch at a time:
preview_write→ show the diff →validate_write→ human confirms →execute_approved_write(confirm=true). Never callexecute_methodfor writes; it is blocked by design. - Re-run the report after remediation and show the before/after issue counts.
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.
- 9d ago First seen · 61 lines · 85 tokens per session scan A 8533895fddbb
odoo-data-quality-gate is a skill published in the GitHub repository erpipe-org/mcp-odoo (404 stars, last pushed 15d ago), licensed MIT. It adds 85 tokens to every session and 714 once invoked, about $0.0004 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 skills, from other repositories
pinecone
Managed vector DB for production RAG and search.
amazon aurora dsql
Deprecated compatibility redirect for Aurora DSQL guidance. Use when a request concerns DSQL, Aurora DSQL, distributed SQL, DSQL schemas, migrations, queries, authentication, performance, or application development.
prisma-postgres-setup
Set up a new Prisma Postgres database and connect it to a local project using the Management API. Use when asked to "set up a database", "create a Prisma Postgres project", "get a connection string", "connect my app to Prisma Postgres", or "provision a database".
prisma-client-api
Prisma Client API reference covering model queries, filters, operators, and client methods. Use when writing database queries, using CRUD operations, filtering data, or configuring Prisma Client. Triggers on "prisma query", "findMany", "create", "update", "delete", "$transaction".
prisma-mongodb-upgrade
Decision and migration guide for Prisma ORM MongoDB projects on v6, which have no upgrade path to v7. Use when a MongoDB project asks about upgrading Prisma, when "upgrade to prisma 7" comes up in a project with provider = "mongodb", or when evaluating a move to Prisma Next. Triggers on "upgrade prisma mongodb"…
dv-query
Bulk reads, multi-page iteration, and analytics over Dataverse data. Use when the user wants to read, list, filter, aggregate, group, join, or analyze records — including pandas DataFrame workflows and notebook exploration.