Borrowing it
Nothing to install: this file belongs to chama-x/GroundRules. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/chama-x/GroundRules/master/.agents/archive/v3/skill_odoo-discipline/skills/odoo/SKILL.mdgit clone --depth 1 https://github.com/chama-x/GroundRulesWrote 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/chama-x/groundrules/odoo)<a href="https://agentmods.dev/skills/chama-x/groundrules/odoo"><img src="https://agentmods.dev/badge/skills/chama-x/groundrules/odoo/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/chama-x/groundrules/odoo"><img src="https://agentmods.dev/badge/skills/chama-x/groundrules/odoo.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.00078 | $0.00689 |
| Opus 5.5 | $0.00031 | $0.00276 |
| Sonnet 5.5 | $0.00016 | $0.00138 |
| Haiku 4.5 | $0.00008 | $0.00069 |
Grade A, and why
odoo 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 1mo 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Odoo
Use this skill only for Odoo work. For OCA module migration or major-version addon ports, route to odoo-migration.
First Move
Explore before asking. Inspect the repo for Odoo signals: __manifest__.py, odoo-bin, addons/, models/, views/, security/ir.model.access.csv, controllers/, static/src/, and project docs.
Before version-sensitive changes, detect the target Odoo version from branch names, manifests, docs, dependencies, or config. If the version is not discoverable, ask. If $ODOO_SOURCE is set, inspect it for framework behavior instead of guessing.
Before running Odoo update/test commands, inspect likely commands from repo docs/config. If $ODOO_TOOL_README is set, read it for local tooling. If $ODOO_BASE_COMMAND is set, use it as the starting point for proposed Odoo commands. Then ask the user to confirm before running commands that touch a database or local service.
Route The Task
- Stress-test an Odoo plan/design before implementation: use
odoo-grill-me. - Build or change addon behavior: use DEVELOPMENT.md.
- Understand an unfamiliar Odoo codebase: use EXPLORATION.md.
- Debug broken Odoo behavior: use DEBUGGING.md.
- Trace a concrete execution path through controllers, buttons, cron jobs, model methods, overrides, computes, onchanges, constraints, or side effects: use
odoo-code-tracer. - Hunt for Odoo architecture/refactor opportunities: use ARCHITECTURE.md.
- Sync manifest/docs with implemented behavior: use MANIFEST-DOCS.md.
- Build, review, debug, or migrate Odoo OWL frontend components: use
odoo-owl. - Review Odoo code for correctness, security, performance, tests, migrations, manifests, and official coding guidelines: use
odoo-code-review. - Create or improve Odoo tests using TransactionCase, HttpCase, Form helper, tags, mocks, access tests, workflow tests, or test coverage patterns: use
odoo-test-writer. - Migrate an OCA addon between Odoo major versions: use
odoo-migration. - Need detailed known-version guidance: use
odoo-17.0,odoo-18.0, orodoo-19.0.
What ships with it
6 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.
- 1mo ago First seen · 36 lines · 78 tokens per session scan A d49a6f6f320e
odoo is a skill published in the GitHub repository chama-x/GroundRules (5 stars, last pushed 2mo ago), licensed MIT. It adds 78 tokens to every session and 689 once invoked, about $0.0003 per session on Opus 5.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
api-debugging
Systematic approach to debugging REST APIs, HTTP errors, authentication issues, and network problems. Use when the user has API errors, status code issues, timeout problems, or needs help troubleshooting HTTP requests.
error-handling
Use when a ticket touches how failures are represented, propagated, or reported — a new error type, a retry, a fallback, "handle the case where X fails", swallowed exceptions, or unclear error messages — and the result must fail loudly where it should and recover only where it can. Invoke for "handle errors properly"…
api-health-checker
Check api health checker operations. Auto-activating skill for API Integration. Triggers on: api health checker, api health checker Part of the API Integration skill category. Use when working with APIs or building integrations. Trigger with phrases like "api health checker", "api checker", "api".
nextjs-server-side-error-debugging
Debug getServerSideProps and getStaticProps errors in Next.js. Use when: (1) Page shows generic error but browser console is empty, (2) API routes return 500 with no details, (3) Server-side code fails silently, (4) Error only occurs on refresh not client navigation. Check terminal/server logs instead of browser for…
agent-crdt-synchronizer
Agent skill for crdt-synchronizer - invoke with $agent-crdt-synchronizer.
api-integration-architect
Design, implement, debug, and optimize API integrations with expert-level patterns for REST, GraphQL, webhooks, and authentication flows.