plugins/odoo-token-killer/SKILL.md
OTK (Odoo Token Killer) - Reduce token consumption by 60-90% on Odoo development operations. Inspired by RTK (Rust Token Killer) by the rtk-ai team. AUTO-USE when running Bash commands during Odoo development. The PreToolUse hook handles transparent rewriting automatically. For manual use, prefix commands with `otk`: otk invoke test my_module → test failures only (90% savings) otk docker compose logs odoo → errors/warnings only (90% savings) otk git status → compact stats (80% savings) otk read models/sale.py → signatures + fields only (60% savings) otk read views/sale_view.xml → structure only (70% savings) otk gain → token savings dashboard Compatible with: odoo-doodba-dev, odoo-development, odoo-query plugins.
npx skillsauth add letzdoo/claude-marketplace odoo-token-killerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Reduce Claude Code token consumption by 60-90% on Odoo development.
Inspired by RTK (Rust Token Killer) by the rtk-ai team. We thank the RTK team for pioneering the token-optimized CLI proxy pattern.
OTK sits between Claude Code and your terminal. When Claude runs commands, OTK's PreToolUse hook transparently intercepts and filters the output:
Claude runs: git status
Hook rewrites: otk git status
Output: "3 modified, 1 added" instead of 50 lines of verbose status
Tokens saved: ~80%
| Operation | Frequency | Without OTK | With OTK | Savings |
|-----------|-----------|-------------|----------|---------|
| invoke test | 5x | 50,000 | 5,000 | -90% |
| docker compose logs | 10x | 30,000 | 3,000 | -90% |
| Reading .py files | 20x | 40,000 | 12,000 | -70% |
| Reading .xml views | 15x | 30,000 | 9,000 | -70% |
| git status/diff/log | 10x | 15,000 | 3,000 | -80% |
| grep/rg searches | 8x | 16,000 | 3,200 | -80% |
| Total | | ~181,000 | ~35,200 | -81% |
| Command | Description |
|---------|-------------|
| /otk-setup | Install OTK and register the PreToolUse hook |
| /otk-gain | Show token savings analytics dashboard |
12 specialized filters, each targeting a specific output type:
OTK works alongside all other Letzdoo plugins:
invoke testtools
Core OTK engine: Rust CLI proxy, output filters, token tracking, and analytics. This skill provides the `otk` binary and all 12 filter strategies. AUTO-TRIGGER: Used automatically via PreToolUse hook - no manual invocation needed. Performance: <10ms startup, <5MB binary, <5MB memory. Written in Rust like RTK.
data-ai
Connect to Odoo instances via XML-RPC for read-only queries to investigate issues and explore data. Use when user asks to "query odoo", "connect to odoo", "investigate odoo data", "read odoo records", or needs to explore an Odoo instance.
tools
--- name: Odoo Indexer description: Fast indexer for Odoo codebases - 95% more token-efficient than reading files. USE AUTOMATICALLY AND PROACTIVELY before ANY Odoo code work. AUTO-TRIGGER when user mentions models (sale.order, res.partner, account.move, etc.), fields (partner_id, name, state, etc.), views (form, tree, kanban), XML IDs, or when you need to search/validate/explore Odoo code. USE BEFORE writing code to validate references exist, USE BEFORE reading files to locate elements, USE DUR
development
MUST be loaded when ANY Odoo development task is detected. CRITICAL: Claude MUST use this skill for ALL tasks involving: - "odoo", "module", "model", "view", "field", "OWL", "manifest" - ANY mention of Odoo versions (14, 15, 16, 17, 18, 19) - "create odoo module", "generate odoo code", "review odoo module" - "upgrade odoo", "odoo best practices", "odoo security" ALWAYS trigger the odoo-context-gatherer agent BEFORE writing ANY Odoo code.