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-grill-me/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-grill-me)<a href="https://agentmods.dev/skills/chama-x/groundrules/odoo-grill-me"><img src="https://agentmods.dev/badge/skills/chama-x/groundrules/odoo-grill-me/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-grill-me"><img src="https://agentmods.dev/badge/skills/chama-x/groundrules/odoo-grill-me.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.00066 | $0.00904 |
| Opus 5 | $0.00033 | $0.00452 |
| Sonnet 5 | $0.00013 | $0.00181 |
| Haiku 4.5 | $0.00007 | $0.00090 |
Grade A, and why
odoo-grill-me 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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Odoo Grill Me
Interview the user relentlessly about every aspect of an Odoo plan until there is shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one by one.
Ask exactly one question at a time. For each question, include your recommended answer.
If a question can be answered by exploring the codebase, inspect the codebase instead of asking.
First Move
Before asking, gather discoverable facts:
- Odoo version and edition if visible from branch/docs/config.
- Addon/module names and manifests.
- Existing models, views, security, data, controllers, assets, tests, and docs relevant to the plan.
$ODOO_SOURCE,$ODOO_TOOL_README, and$ODOO_BASE_COMMANDcontext when available.
Then ask the highest-leverage unresolved question.
Question Branches
Use only the branches relevant to the plan.
Product And Workflow
- What user workflow is being changed?
- Which users/groups need it?
- What should happen in draft, confirmed, cancelled, archived, or error states?
- What business invariant must never be violated?
Module Boundary
- Which addon owns the concept?
- Is this a new addon, extension of an existing addon, or configuration/data-only change?
- Which manifest dependencies are real, and which would be convenience dependencies?
- Does the plan couple unrelated business domains?
Model Design
- Is this a new model,
_inherit, or_inherits? - What is the lifecycle of the record?
- Which fields are stored, computed, related, required, tracked, or company-dependent?
- Which constraints belong in Python, SQL, views, or onchange?
- Which methods are stable seams for future extension?
Security And Access
- Which groups can read, create, write, and unlink?
- Are record rules needed, and are they multi-company safe?
- Is any
sudo()required? If yes, why is access elevation correct? - Are portal/public users or controllers exposed?
- What data could leak across companies, websites, portals, or users?
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 · 113 lines · 66 tokens per session scan A c936df057384
odoo-grill-me is a skill published in the GitHub repository chama-x/GroundRules (5 stars, last pushed 25d ago), licensed MIT. It adds 66 tokens to every session and 904 once invoked, about $0.0003 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-31.
Other skills, from other repositories
github
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available)…
repo-audit
Run a comprehensive language-agnostic repository health audit, scored 0-100. Detects language, runs native tooling, never assumes JS/Python.
github
Full GitHub CLI control — issues, PRs, code reviews, repo management. Uses gh CLI with auth detection, rate limiting, and templates. Triggers on: github, issue, pull request, PR, code review, repo, branch, label, assignee, milestone, release, workflow, actions.
cleanup-audit
Audit codebase for dead code, unused exports, orphaned files, and stale manifests.
link-check
Verify @file references in AIWG skills and agents against the linking contract — per-file or corpus-wide, with optional auto-fix.
iterative-converging-audit
Run any "find all instances of X" sweep — a security audit, a safety audit, a code review, a research question, a compliance check — as an iterative loop that does NOT stop at one pass. Audit → fix → RE-audit → … until a clean pass returns zero NEW discoveries. Use whenever thoroughness matters and a single pass would…