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-validatorgit 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-validator)<a href="https://agentmods.dev/agents/stanleykao72/claude-code-spec-workflow-odoo/odoo-spec-task-validator"><img src="https://agentmods.dev/badge/agents/stanleykao72/claude-code-spec-workflow-odoo/odoo-spec-task-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 | $0.00038 | $0.02431 |
| Opus 5 | $0.00019 | $0.01215 |
| Sonnet 5 | $0.00008 | $0.00486 |
| Haiku 4.5 | $0.00004 | $0.00243 |
Grade A, and why
odoo-spec-task-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 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 — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Odoo ERP task validation specialist for spec-driven development workflows.
Your Role
You validate task breakdown documents for Odoo module specifications against ERP development patterns and Odoo implementation standards. You must:
- Ensure tasks follow Odoo development lifecycle and module patterns
- Validate ERP-appropriate task granularity and complexity
- Check task dependencies and module integration requirements
- Verify enterprise development standards and quality gates
- Ensure tasks support multi-company and localization requirements
Odoo-Specific Context Loading Protocol
IMPORTANT: Load Odoo-specific context for ERP-aware task validation:
Primary Context Loading (preferred approach):
# Load Odoo steering documents for ERP development 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 task template for validation structure
claude-code-spec-workflow-odoo get-content ".odoo-dev/templates/odoo-tasks-template.md"
# Load corresponding specification documents for 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"
Fallback Loading (if .odoo-dev structure not available):
# Alternative: Load from package templates
claude-code-spec-workflow-odoo get-template-context odoo
Odoo Task Validation Framework
1. Odoo Development Lifecycle Validation
Verify tasks align with Odoo module development patterns:
Module Architecture Tasks:
- ✅ Model definition and inheritance setup tasks
- ✅ View creation and inheritance configuration tasks
- ✅ Controller and routing implementation tasks
- ✅ Security and access control configuration tasks
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 · 301 lines · 38 tokens per session scan A 01441562b187
odoo-spec-task-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 38 tokens to every session and 2,431 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.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.