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 commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-spec-executegit 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-spec-execute)<a href="https://agentmods.dev/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-spec-execute"><img src="https://agentmods.dev/badge/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-spec-execute.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.01465 |
| Opus 5 | $0.00000 | $0.00732 |
| Sonnet 5 | $0.00000 | $0.00293 |
| Haiku 4.5 | $0.00000 | $0.00146 |
Grade A, and why
odoo-spec-execute 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 6d 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
odoo-spec-execute - Execute Odoo Module Specification Tasks
Execute specific tasks within Odoo module specifications, providing module-aware context and execution.
Usage
/odoo-spec-execute <task-id> <spec-name> [module-name]
Parameters:
task-id: Task number to execute (e.g., 1, 2, 3)spec-name: Name of the specification (feature, bug fix, or test)module-name(optional): Specific module name if spec name is ambiguous
Examples:
/odoo-spec-execute 1 inventory-tracking
/odoo-spec-execute 2 inventory-tracking inventory_custom
/odoo-spec-execute 3 stock-enhancement warehouse_mgmt
What This Command Does
This command executes specific tasks within Odoo module specifications, providing full module context including dependencies, inheritance chains, and Odoo-specific development patterns.
Instructions
Use the @odoo-spec-task-executor agent to execute Odoo module specification tasks:
Execute Odoo module specification task with complete module context:
# 1. Module and Specification Discovery
- Locate the specification within the module's .spec/ directory structure
- Determine spec type (features/, bugs/, testing/)
- Validate task ID exists in tasks.md file
- Load module configuration and metadata
# 2. Comprehensive Context Loading
Load complete development context for the task:
## Module Context (.odoo-dev/config.json)
- Module technical name and path
- Odoo version compatibility
- Module dependencies and relationships
- Development environment settings
## Steering Documents (.odoo-dev/steering/)
- business-rules.md: ERP business logic and workflow standards
- technical-stack.md: Odoo technical guidelines and patterns
- module-standards.md: Custom module development standards
## Specification Context ([module-path]/.spec/)
- For Features: request.md + requirements.md + design.md + tasks.md
- For Bugs: report.md + analysis.md + fix.md + verification.md
- For Tests: testing-plan.md + test-cases.md + test-implementation.md
## Task-Specific Context
- Extract specific task details from tasks.md
- Load task dependencies and prerequisites
- Identify task-specific requirements and acceptance criteria
# 3. Odoo Development Context
Provide Odoo-specific development context:
## Module Architecture Analysis
- Existing model inheritance chains
- View hierarchy and customizations
- Security rules and access controls
- Data files and demo data
## Integration Points
- Dependencies on other modules
- Integration with Odoo core modules
- Third-party module interactions
- Database schema impact
## Development Patterns
- Follow Odoo coding conventions (PEP 8, Odoo guidelines)
- Apply appropriate inheritance patterns (_inherit vs _inherits)
- Use Odoo ORM best practices
- Implement proper security and access controls
# 4. Task Execution with Module Awareness
Execute the task with full module context:
## Code Implementation
- Follow module's existing code structure and patterns
- Implement using appropriate Odoo frameworks (models, views, controllers)
- Ensure compatibility with module's Odoo version
- Apply module-specific naming conventions
## File Management
- Create/modify files within the module directory
- Follow module's directory structure conventions
- Update __init__.py and __manifest__.py as needed
- Maintain proper file organization
## Quality Assurance
- Follow module's coding standards
- Implement appropriate error handling
- Add necessary logging and debugging
- Include security considerations
## Testing Integration
- Create or update relevant tests
- Follow pytest-odoo conventions if applicable
- Ensure tests fit module's testing strategy
- Validate against module's quality standards
# 5. Task Completion and Documentation
## Progress Updates
- Mark task as completed in tasks.md
- Update implementation status and notes
- Document any issues or decisions made
- Note any dependencies or follow-up tasks
## Next Steps Guidance
- Identify next task in the specification
- Highlight any blockers or dependencies
- Suggest testing or verification steps
- Recommend integration testing if applicable
# 6. Module Integration Validation
Before marking complete, validate:
- Module loads without errors
- No conflicts with existing functionality
- Proper integration with dependent modules
- Follows module's upgrade path compatibility
# 7. Output Format
Provide comprehensive execution report:
🚀 TASK EXECUTION: [module-name]/[spec-name] - Task [task-id]
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.
- 6d ago First seen · 206 lines · 0 tokens per session scan A 379bfa1f32bf
odoo-spec-execute 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 1,465 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.