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/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-steering)<a href="https://agentmods.dev/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-steering"><img src="https://agentmods.dev/badge/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-steering.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.00000 | $0.00617 |
| Opus 5 | $0.00000 | $0.00309 |
| Sonnet 5 | $0.00000 | $0.00123 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
odoo-steering 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
odoo-steering - Generate Odoo-Specific Steering Documents
Generate comprehensive steering documents specifically for Odoo ERP projects, including business rules, technical standards, and module development guidelines.
Usage
/odoo-steering
What This Command Does
This command generates Odoo-specific steering documents that provide:
- Business Rules Document: ERP-specific business logic and workflows
- Technical Stack Document: Odoo development standards and patterns
- Module Standards Document: Guidelines for custom module development
Instructions
Use the @odoo-spec-task-executor agent to generate Odoo steering documents:
Generate comprehensive Odoo steering documents using odoo-product-template.md and create in project-level configuration directory:
# Generated Files Structure:
Create in .odoo-dev/steering/:
- business-rules.md: ERP business logic standards and workflow rules
- technical-stack.md: Odoo technical guidelines and development patterns
- module-standards.md: Custom module development standards and best practices
# 1. Business Rules Document (.odoo-dev/steering/business-rules.md)
- ERP workflow standards and business process integration
- Multi-company data policies and isolation rules
- User role definitions and permission matrices
- Data validation and integrity requirements
- Localization and compliance standards
# 2. Technical Stack Document (.odoo-dev/steering/technical-stack.md)
- Odoo development patterns (Model-View-Controller architecture)
- Database design standards (PostgreSQL optimization)
- Security framework implementation guidelines
- API design guidelines (REST/JSON-RPC best practices)
- Performance optimization and scalability standards
# 3. Module Standards Document (.odoo-dev/steering/module-standards.md)
- Module structure and naming conventions
- Model inheritance best practices (_inherit vs _inherits)
- View design patterns (form, tree, kanban, search)
- Security rule implementation standards
- Testing standards (pytest-odoo integration)
- Documentation and version control requirements
These steering documents will be used by all subsequent /odoo-spec-create, /odoo-bug-fix, and /odoo-feature-create commands to ensure project-wide consistency.
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 · 72 lines · 0 tokens per session scan A 0662d0a7b5ca
odoo-steering is a command published in the GitHub repository stanleykao72/claude-code-spec-workflow-odoo (44 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 617 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.