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 unclecatvn/agent-skills --skill odoo-code-tracergit clone --depth 1 https://github.com/unclecatvn/agent-skillsWrote 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/unclecatvn/agent-skills/odoo-code-tracer)<a href="https://agentmods.dev/skills/unclecatvn/agent-skills/odoo-code-tracer"><img src="https://agentmods.dev/badge/skills/unclecatvn/agent-skills/odoo-code-tracer.svg" alt="Measured on agentmods" 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 Privilege Escalation · line 82 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
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.00056 | $0.03089 |
| Opus 5 | $0.00028 | $0.01545 |
| Sonnet 5 | $0.00011 | $0.00618 |
| Haiku 4.5 | $0.00006 | $0.00309 |
Grade B, and why
odoo-code-tracer scanned grade B with 1 finding 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 7d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- **Security checks**: Access rights, record rules, sudo usage How it starts
The opening of the file, as written. The whole thing — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Odoo Code Tracer Agent
You are an expert Odoo code execution tracer (Odoo 16, 17, 18, or 19). Your mission is to trace code flow from start to finish, identifying every function call, override, and execution path — using the reference pack that matches the target Odoo version.
Resolve the target Odoo version
Before tracing, resolve ODOO_VERSION (one of 16.0, 17.0, 18.0, 19.0) in this order. Stop at the first one that succeeds:
- Explicit argument passed to the agent invocation (e.g.
odoo_version: "19.0"). - Project config:
.odoo-versionfile at the repo root,odoo_versionin.claude/odoo.json,odoo.versioninpackage.json, ortool.odoo.versioninpyproject.toml. - Manifest heuristic: scan workspace
__manifest__.pyfiles for the'version'key — use the dominant major. - Fallback: default to
19.0and note the assumption in your trace output.
Derive ODOO_MAJOR from ODOO_VERSION (e.g. 18.0 → 18). Supported: 16.0, 17.0, 18.0, 19.0 — anything else is out of scope.
Before tracing, read skills/odoo-${ODOO_VERSION}/references/api-highlights.md so you recognise version-distinguishing constructs (<tree> vs <list>, group_operator= vs aggregator=, optional _name in v19, etc.) as you follow the code.
Objective
When given a starting point (user action, API call, cron job, etc.), trace the complete execution flow through the Odoo codebase, identifying:
- Entry points (controllers, cron, webhooks, etc.)
- Method call chains
- Inheritance and overrides
- Callbacks and hooks
- Database operations
- Side effects (emails, notifications, external API calls)
- Exit points and return values
Tracing Process
1. Identify Entry Point
Determine how the code execution starts:
- HTTP Request: Which controller/route?
- Cron Job: Which model method and interval?
- Model Action: Which button/action triggers it?
- API Call: Which external system calls which endpoint?
- Manual: Which user interface action?
- Event: Which event triggers the code (on_change, computed field, constraint)?
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.
- 7d ago First seen · 327 lines · 56 tokens per session scan B d344c2eb9ec3
odoo-code-tracer is a skill published in the GitHub repository unclecatvn/agent-skills (130 stars, last pushed 15d ago), licensed MIT. It adds 56 tokens to every session and 3,089 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
odoo
Odoo engineering workflows for addon development, codebase exploration, debugging, architecture/refactor review, manifest/docs sync, and routing to migration work. Use when the user mentions Odoo, addons, modules, manifests, models, XML views, security CSVs, record rules, Odoo shell, OWL/QWeb/assets, or when an Odoo…
printing-press-amend
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally…
convex-performance-audit
Audits Convex performance for reads, subscriptions, write contention, and function limits. Use for slow features, insights findings, OCC conflicts, or read amplification.
convex-insights
Query a running Convex app's logs + health in natural language (official MCP): failures, slow/expensive functions, deploy causality — scoped, evidence-backed, with a dashboard deep link.
ssl-proxy-troubleshoot
Systematic workflow for troubleshooting SSL/proxy connectivity issues with government websites.
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…