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-code-tracer/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-code-tracer)<a href="https://agentmods.dev/skills/chama-x/groundrules/odoo-code-tracer"><img src="https://agentmods.dev/badge/skills/chama-x/groundrules/odoo-code-tracer/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-code-tracer"><img src="https://agentmods.dev/badge/skills/chama-x/groundrules/odoo-code-tracer.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.00071 | $0.01268 |
| Opus 5.5 | $0.00028 | $0.00507 |
| Sonnet 5.5 | $0.00014 | $0.00254 |
| Haiku 4.5 | $0.00007 | $0.00127 |
Grade A, and why
odoo-code-tracer 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Odoo Code Tracer
Use this skill to map how Odoo code actually executes. Trace only what you can verify in code. If a path is uncertain, mark it as uncertain and explain what evidence is missing.
First Move
Identify the starting point:
- HTTP route or controller
- form/list button action
- server action or automated action
- cron job
- ORM method called by another addon
- compute, onchange, constraint, inverse, or create/write/unlink hook
- report render
- OWL/web client action calling backend code
- external webhook or integration callback
Detect the target Odoo version. If a version-specific reference exists, consult it before tracing version-sensitive behavior:
- Odoo 17:
odoo-17.0 - Odoo 18:
odoo-18.0 - Odoo 19:
odoo-19.0
If $ODOO_SOURCE is set, inspect local framework code for controller dispatch, ORM behavior, decorators, web client actions, assets, tests, and version-specific execution details.
Tracing Process
- Locate the entry point with file and line reference.
- Follow the direct method call chain.
- Follow inheritance and
super()calls through parent implementations. - Check decorators and implicit triggers:
@api.depends,@api.constrains,@api.onchange, inverse methods,@api.ondelete, create/write/unlink overrides. - Follow XML wiring: buttons, actions, menus, reports, cron records, server actions, and external IDs.
- Follow frontend wiring when relevant: asset bundle, JS module, registry entry, service call, RPC/ORM call, template event.
- Record database operations:
search,browse,read,read_group,create,write,unlink, direct SQL, savepoints, locks. - Record side effects: chatter, emails, notifications, activities, reports, attachments, external API calls, queue jobs, bus events.
- Record security checks: auth mode, ACLs, record rules, groups, domains, company filters,
sudo()boundaries. - Mark exit points and returned actions/data.
What To Watch For
- N+1 queries from searches, browses, reads, creates, writes, or unlinks inside loops.
- Hidden side effects from computed fields, constraints, onchange methods, mail mixins, activities, and automation.
- Unsafe
sudo()that bypasses ownership, company, portal, or public-user boundaries. - Fragile XML linkage through renamed methods, missing external IDs, or version-specific view syntax.
- Transaction hazards from caught database exceptions without savepoints.
- Business rules split across views, onchanges, controllers, and scheduled actions.
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 · 116 lines · 71 tokens per session scan A 832efca471fc
odoo-code-tracer is a skill published in the GitHub repository chama-x/GroundRules (5 stars, last pushed 2mo ago), licensed MIT. It adds 71 tokens to every session and 1,268 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
agent-performance-optimizer
Agent skill for performance-optimizer - invoke with $agent-performance-optimizer.
agent-refinement
Agent skill for refinement - invoke with $agent-refinement.
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
triage-issue
Analyze a GitHub issue, verify claims against the codebase, and close invalid issues with a technical response.
node-connect
Diagnose Brigade node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale…
hive.error-recovery
Follow a structured recovery decision tree when tool calls fail instead of blindly retrying or giving up.