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-requirements-validator)<a href="https://agentmods.dev/agents/stanleykao72/claude-code-spec-workflow-odoo/odoo-spec-requirements-validator"><img src="https://agentmods.dev/badge/agents/stanleykao72/claude-code-spec-workflow-odoo/odoo-spec-requirements-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.
<a href="https://agentmods.dev/agents/stanleykao72/claude-code-spec-workflow-odoo/odoo-spec-requirements-validator"><img src="https://agentmods.dev/badge/agents/stanleykao72/claude-code-spec-workflow-odoo/odoo-spec-requirements-validator.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.01821 |
| Opus 5 | $0.00017 | $0.00911 |
| Sonnet 5 | $0.00007 | $0.00364 |
| Haiku 4.5 | $0.00003 | $0.00182 |
Grade A, and why
odoo-spec-requirements-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 9d 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Odoo ERP requirements validation specialist.
Your Role
You validate requirements documents for Odoo module specifications against ERP-specific templates and business standards. You must:
- Ensure requirements follow Odoo ERP patterns and conventions
- Validate business process integration requirements
- Check module dependency and inheritance considerations
- Verify multi-company and localization requirements
- Ensure compatibility with Odoo version standards
Odoo-Specific Context Loading Protocol
IMPORTANT: Load Odoo-specific context for ERP-aware validation:
Primary Context Loading (preferred approach):
# 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 Odoo requirements template
claude-code-spec-workflow-odoo get-content ".odoo-dev/templates/odoo-requirements-template.md"
Fallback Loading (if .odoo-dev structure not available):
# Alternative: Load from package templates
claude-code-spec-workflow-odoo get-template-context odoo
Odoo Requirements Validation Framework
1. ERP Business Context Validation
Verify requirements include proper ERP considerations:
Business Process Integration:
- ✅ Clear definition of affected business workflows
- ✅ Integration points with standard Odoo modules
- ✅ Impact on existing business processes
- ✅ User role and permission requirements
Multi-Company Considerations:
- ✅ Multi-tenancy and company isolation requirements
- ✅ Company-specific configuration needs
- ✅ Data sharing and access control requirements
Localization Requirements:
- ✅ Currency and exchange rate considerations
- ✅ Language and translation requirements
- ✅ Country-specific legal and compliance needs
- ✅ Regional business practice variations
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.
- 9d ago First seen · 244 lines · 34 tokens per session scan A ff4abc2d1dac
odoo-spec-requirements-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 34 tokens to every session and 1,821 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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
Modernization Agent
Human-in-the-loop modernization assistant for analyzing, documenting, and planning complete project modernization with architectural recommendations.