What is odoo-spec-design-validator?

A design-validation agent for Odoo ERP modules, which are extensions for business-management software. It checks technical designs against Odoo architecture, business processes, integrations, security, and performance needs.

Reviewing Odoo module specifications, validating MVC and ORM designs, checking inheritance and dependencies, and assessing integrations, permissions, and performance.

It helps find design problems before implementation, including incorrect Odoo patterns, missing dependencies, weak access controls, and scalability gaps.

odoo-spec-design-validator — Agent for Claude Code by stanleykao72

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/stanleykao72/claude-code-spec-workflow-odoo

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/stanleykao72/claude-code-spec-workflow-odoo/odoo-spec-design-validator/github.svg)](https://agentmods.dev/agents/stanleykao72/claude-code-spec-workflow-odoo/odoo-spec-design-validator)

Your own site

<a href="https://agentmods.dev/agents/stanleykao72/claude-code-spec-workflow-odoo/odoo-spec-design-validator"><img src="https://agentmods.dev/badge/agents/stanleykao72/claude-code-spec-workflow-odoo/odoo-spec-design-validator/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/stanleykao72/claude-code-spec-workflow-odoo/odoo-spec-design-validator"><img src="https://agentmods.dev/badge/agents/stanleykao72/claude-code-spec-workflow-odoo/odoo-spec-design-validator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,250 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 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.

Model	Per session	Once invoked
Fable 5.1	$0.00036	$0.02250
Opus 5.5	$0.00014	$0.00900
Sonnet 5.5	$0.00007	$0.00450
Haiku 4.5	$0.00004	$0.00225

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

Security

Grade A, and why

odoo-spec-design-validator 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 2mo 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.

src/markdown/agents/odoo-spec-design-validator.md · 290 lines

How it starts

The opening of the file, as written. The whole thing — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are an Odoo ERP design validation specialist.

Your Role

You validate technical design documents for Odoo module specifications against ERP architecture patterns and Odoo development standards. You must:

Ensure designs follow Odoo MVC architecture and ORM patterns
Validate ERP integration and business process alignment
Check module inheritance patterns and dependency management
Verify security model and access control design
Ensure performance and scalability considerations for ERP systems

Odoo-Specific Context Loading Protocol

IMPORTANT: Load Odoo-specific context for ERP-aware design validation:

Primary Context Loading (preferred approach):

# Load Odoo steering documents for ERP architecture 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 Odoo design template
claude-code-spec-workflow-odoo get-content ".odoo-dev/templates/odoo-design-template.md"

# Load corresponding requirements for context
claude-code-spec-workflow-odoo get-content "[module-path]/.spec/features/[feature-name]/requirements.md"

Fallback Loading (if .odoo-dev structure not available):

# Alternative: Load from package templates  
claude-code-spec-workflow-odoo get-template-context odoo

Odoo Design Validation Framework

1. Odoo Architecture Compliance Validation

Verify design follows Odoo architectural patterns:

Model-View-Controller (MVC) Architecture:

✅ Models properly inherit from odoo.models.Model
✅ Views follow Odoo XML structure and inheritance patterns
✅ Controllers use proper routing and authentication
✅ Business logic appropriately distributed across MVC layers

ORM Integration Design:

✅ Field definitions use appropriate Odoo field types
✅ Relationships use correct Many2one/One2many/Many2many patterns
✅ Computed fields have proper dependencies and caching
✅ Constraints and validations follow Odoo conventions

Read the full file on GitHub · 290 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.

2mo ago First seen · 290 lines · 36 tokens per session scan A 06009d1573ed

Subscribe to this mod's changes

odoo-spec-design-validator is an agent published in the GitHub repository stanleykao72/claude-code-spec-workflow-odoo (44 stars, last pushed 1y ago), licensed MIT. It adds 36 tokens to every session and 2,250 once invoked, about $0.0001 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-30.

Code review

odoo-spec-design-validator next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
odoo-spec-design-validatorstanleykao72/claude-code-spec-workflow-odoo	Agent	44	1y ago	MIT	A	36	Claude Code
cpp-revieweraffaan-m/ECC	Agent	299k	today	MIT	A	41	Claude Code, Kiro
thermo-nuclear-code-quality-review-subagentmichael-denyer/pstack-claude	Agent	4.1k	yesterday	MIT	A	68	Claude Code
review-obsidian-guidelinesuphy/obsidian-reminder	Agent	662	2d ago	MIT	A	63	Claude Code
karimo-implementeropensesh/KARIMO	Agent	290	25d ago	Apache-2.0	A	49	Claude Code
atomic-auditordamusix/atomic-claude	Agent	116	5d ago	MIT	A	169	Claude Code
reviewergenkovich/sdd	Agent	199	22d ago	MIT	A	81	Claude Code