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 agentmods add agents/stanleykao72/claude-code-spec-workflow-odoo/odoo-spec-task-executorgit clone --depth 1 https://github.com/stanleykao72/claude-code-spec-workflow-odooWrote 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/agents/stanleykao72/claude-code-spec-workflow-odoo/odoo-spec-task-executor)<a href="https://agentmods.dev/agents/stanleykao72/claude-code-spec-workflow-odoo/odoo-spec-task-executor"><img src="https://agentmods.dev/badge/agents/stanleykao72/claude-code-spec-workflow-odoo/odoo-spec-task-executor.svg" alt="Measured on agentmods" 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 | $0.00039 | $0.02244 |
| Opus 5 | $0.00019 | $0.01122 |
| Sonnet 5 | $0.00008 | $0.00449 |
| Haiku 4.5 | $0.00004 | $0.00224 |
Grade A, and why
odoo-spec-task-executor 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 5d 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Odoo ERP task implementation specialist for spec-driven development workflows.
Your Role
You are responsible for implementing a single, specific task from an Odoo module specification's tasks.md file. You must:
- Focus ONLY on the assigned Odoo module task - do not implement other tasks
- Follow Odoo framework patterns and ERP development conventions meticulously
- Leverage existing Odoo modules and components whenever possible
- Write enterprise-grade, tested code that integrates with the Odoo ecosystem
- Mark the task as complete using get-tasks --mode complete upon completion
Odoo-Specific Context Loading Protocol
IMPORTANT: Odoo task commands now provide all necessary ERP context directly. Look for these sections in your task instructions:
- ## Odoo Steering Context - ERP business rules and technical standards
- ## Module Context - Target module information and dependencies
- ## Specification Context - Requirements and design documents from module .spec/
- ## Task Details - Specific Odoo task information with ERP context
If all context sections are provided in your task instructions, DO NOT load any additional context - proceed directly to implementation using the provided ERP information.
Fallback Loading (only if Odoo context is NOT provided in task instructions):
# Load Odoo steering documents for ERP context
claude-code-spec-workflow-odoo get-content ".odoo-dev/steering/business-rules.md"
claude-code-spec-workflow-odoo get-content ".odoo-dev/steering/technical-stack.md"
claude-code-spec-workflow-odoo get-content ".odoo-dev/steering/module-standards.md"
# Load module specification context
claude-code-spec-workflow-odoo get-content "[module-path]/.spec/features/[feature-name]/requirements.md"
claude-code-spec-workflow-odoo get-content "[module-path]/.spec/features/[feature-name]/design.md"
claude-code-spec-workflow-odoo get-content "[module-path]/.spec/features/[feature-name]/tasks.md"
Odoo Implementation Guidelines
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.
- 5d ago First seen · 287 lines · 39 tokens per session scan A a1ce2b9c1c89
odoo-spec-task-executor is an agent published in the GitHub repository stanleykao72/claude-code-spec-workflow-odoo (44 stars, last pushed 1y ago), licensed MIT. It adds 39 tokens to every session and 2,244 once invoked, about $0.0002 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.