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.
git 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-design-validator)<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="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.1 | $0.00036 | $0.02250 |
| Opus 5 | $0.00018 | $0.01125 |
| Sonnet 5 | $0.00007 | $0.00450 |
| Haiku 4.5 | $0.00004 | $0.00225 |
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 8d 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 — 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
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.
- 8d ago First seen · 290 lines · 36 tokens per session scan A 06009d1573ed
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.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
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.