odoo-code-tracer

odoo-code-tracer is an agent for Claude Code from unclecatvn/agent-skills. It costs 56 tokens per session (4,216 once invoked), scanned C, original, MIT.

A code-tracing agent for Odoo, a business application framework written largely in Python. It follows execution from an entry point through calls, overrides, inheritance, and callbacks for Odoo versions 16 through 19.

In plain words
What is it for?
Use it to understand Odoo features end to end, investigate behaviour, and prepare or review changes with the correct Odoo version in mind.
Why use it?
It helps reveal the full path a feature takes instead of relying on a single function or file, reducing missed overrides and unexpected execution paths.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; reads .claude/ paths; mentions CLAUDE.md.

Part of the agent-skills plugin — 7 skills, 2 agents shipped together

Good fit Use it to understand Odoo features end to end, investigate behaviour, and prepare or review changes with the correct Odoo version in mind.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/unclecatvn/agent-skills/odoo-code-tracer
Install

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.

Clone the repo
git clone --depth 1 https://github.com/unclecatvn/agent-skills

Made for: Claude Code.

Or install agent-skills, the plugin that ships this one along with the rest of its 7 skills, 2 agents.

Wrote 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.

agentmods badge for odoo-code-tracer

README.md
[![agentmods](https://agentmods.dev/badge/agents/unclecatvn/agent-skills/odoo-code-tracer/github.svg)](https://agentmods.dev/agents/unclecatvn/agent-skills/odoo-code-tracer)
Your own site
<a href="https://agentmods.dev/agents/unclecatvn/agent-skills/odoo-code-tracer"><img src="https://agentmods.dev/badge/agents/unclecatvn/agent-skills/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.

agentmods 80×15 button for odoo-code-tracer

Your own site · 80×15
<a href="https://agentmods.dev/agents/unclecatvn/agent-skills/odoo-code-tracer"><img src="https://agentmods.dev/badge/agents/unclecatvn/agent-skills/odoo-code-tracer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,216 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00056 $0.04216
Opus 5.5 $0.00022 $0.01686
Sonnet 5.5 $0.00011 $0.00843
Haiku 4.5 $0.00006 $0.00422

Measured 1mo ago against content hash 84073cba3640, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

odoo-code-tracer scanned grade C with 2 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.

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

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

4. **Without the helper**: `grep -n "^version_info" <odoo_root>/odoo/release.py` (`(18, 0, ...)` → `18.0`) in the core located by `odoo_root` in `.claude/odoo.json`, the `odoo-bin` configuration in `.claude/launch.json`
Origin

Copies of this mod

1 near-identical copy found in the catalogue:

agents/odoo-code-tracer.md · 341 lines

How it starts

The opening of the file, as written. The whole thing — 341 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:

  1. Explicit argument passed to the agent invocation (e.g. odoo_version: "19.0") or stated by the user.
  2. Project instructions: the Odoo version stated in the project CLAUDE.md or AGENTS.md.
  3. The odoo-workflow helper: the version line of python3 <helper> env, where <helper> is the helper the invocation passes (with its flags) or the newest ~/.claude/plugins/cache/unclecat-agent-skills/agent-skills/*/skills/odoo-workflow/scripts/odoo_trace.py. It reads .claude/odoo.json, .odoo-version, .claude/launch.json and the conf the way step 4 describes. Exit 2 (SETUP ERROR, for example a version in .claude/odoo.json or .odoo-version that disagrees with odoo/release.py): stop and ask.
  4. Without the helper: grep -n "^version_info" <odoo_root>/odoo/release.py ((18, 0, ...) → 18.0) in the core located by odoo_root in .claude/odoo.json, the odoo-bin configuration in .claude/launch.json whose addons path covers the cwd, or the one *.conf whose uncommented addons_path covers the cwd, searched from the parent directory upwards (each level and its subdirectories; Odoo ignores # / ; comment lines). An odoo_version in .claude/odoo.json or the first line of a .odoo-version file (cwd or nearest parent) must match it.
  5. Serie-prefixed manifest versions: only version values ('version' or "version" keys) in workspace __manifest__.py files with four or five parts that start with the serie (18.0.1.0, 18.0.1.0.0). Ignore short versions such as '1.2' or '1.0.3'; never count leading numbers.
  6. Nothing found: write version unknown in the trace output and stop to ask. Never default to a version.

Read the full file on GitHub · 341 lines

Changes

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.

  1. 1mo ago Changed · +14 lines scan B → C 84073cba3640
  2. 1mo ago First seen · 327 lines · 56 tokens per session scan B d344c2eb9ec3

Subscribe to this mod's changes

odoo-code-tracer is an agent published in the GitHub repository unclecatvn/agent-skills (149 stars, last pushed 10d ago), licensed MIT. It adds 56 tokens to every session and 4,216 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 2 findings (asks for root, reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-12.

Related

Other agents, from other repositories

call-tracer

Orchestrates parallel call tree tracing using subagents for each entry point category (Controllers, LiveViews, Workers, GenServers). Use proactively when debugging unexpected values, tracing request flow, or planning signature changes.

oliver-kriska/claude-elixir-phoenix · 46 tokens

boss-architect

A software architecture reviewer and designer that researches technology choices before creating a full-stack plan. Full-stack means covering the user interface, server, database, and deployment environment.

echoVic/boss-skill · 62 tokens

integration-prober

External service integration verifier. Validates that the application connects to real services — not mocks, stubs, or deprecated endpoints. Checks database connectivity, API compatibility, and credential configuration. Read-only — produces findings, never code.

irahardianto/awesome-agv · 49 tokens

otel-architect

Architect and harden the telemetry layer of a Python service. TRIGGER WHEN: instrumenting, implementing, writing, coding, or building code with OpenTelemetry, designing distributed tracing, auditing observability pipelines, configuring OTLP exporters and Collectors, wiring context propagation over custom transports…

acaprino/daodan · 76 tokens

drupal-ddev

Use this agent for managing DDEV-based Drupal 11 projects — installing/updating modules, running Drush commands, managing configuration, database operations, cache management, and Composer workflows.

siva01c/claude-plugins · 41 tokens

backend-analyzer

Analyze backend services, business logic, and server-side code for inefficient algorithms, blocking operations, or unnecessary computations. Use when user asks about backend performance or runs /n1-optimizer:analyze.

hculap/better-code · 44 tokens