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-module-testgit 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-module-test)<a href="https://agentmods.dev/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-module-test"><img src="https://agentmods.dev/badge/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-module-test.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.01093 |
| Opus 5 | $0.00000 | $0.00547 |
| Sonnet 5 | $0.00000 | $0.00219 |
| Haiku 4.5 | $0.00000 | $0.00109 |
Grade A, and why
odoo-module-test 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
odoo-module-test - Create Odoo Module Testing Specification
Create comprehensive testing specifications for Odoo modules with pytest-odoo integration and ERP-specific test scenarios.
Usage
/odoo-module-test [module-name] "Test description"
Examples
/odoo-module-test inventory_custom "Run tests for custom inventory module"
/odoo-module-test website_custom "Test custom website module functionality"
/odoo-module-test hr_attendance_mobile "Test mobile HR attendance integration"
What This Command Does
This command creates comprehensive testing specifications for Odoo modules including:
- Test Strategy Planning: Unit, integration, and UI testing approach
- pytest-odoo Integration: Proper test configuration for Odoo environment
- ERP-Specific Scenarios: Multi-company, workflow, and data integrity tests
- Performance Testing: Load testing for critical ERP operations
- Migration Testing: Upgrade path validation
Instructions
Use the @odoo-spec-task-executor agent to create Odoo module testing specifications:
Create comprehensive Odoo module testing specification:
# Testing Framework Structure
## 1. Test Environment Setup
- **Database Configuration**: Isolated test database setup
- **pytest-odoo Configuration**: Proper pytest.ini and conftest.py
- **Test Data**: Fixtures and sample data for testing
- **Module Dependencies**: Ensure all required modules are loaded
## 2. Unit Testing Strategy
- **Model Tests**:
- Field validation and constraints
- Compute method accuracy
- Onchange trigger validation
- CRUD operations testing
- **Business Logic Tests**:
- Method return values
- Exception handling
- Edge case validation
- Data consistency checks
## 3. Integration Testing
- **Cross-Module Testing**:
- Workflow integration with core modules
- API endpoint testing
- Webhook functionality
- Scheduled action execution
- **Multi-Company Testing**:
- Data isolation validation
- Company-specific rule enforcement
- Cross-company data access restrictions
## 4. User Interface Testing
- **Tour Scripts**:
- Complete user workflow testing
- Form submission validation
- Navigation and menu testing
- JavaScript widget functionality
- **View Rendering**:
- Form view layout validation
- Tree view filtering and search
- Kanban view drag-and-drop
- Dashboard and report generation
## 5. Performance Testing
- **Load Testing**:
- Database query optimization
- Large dataset handling
- Concurrent user simulation
- Memory usage monitoring
- **Benchmarking**:
- Response time measurement
- Database query analysis
- Resource utilization tracking
## 6. Data Migration Testing
- **Upgrade Path Validation**:
- Data migration script testing
- Field mapping verification
- Data integrity preservation
- Rollback procedure validation
## 7. Security Testing
- **Access Rights Validation**:
- User permission enforcement
- Record rule effectiveness
- API access control
- Data privacy compliance
## 8. Test Execution Plan
- **Local Development**: Running tests during development
- **Continuous Integration**: Automated testing on code changes
- **Staging Environment**: Full integration testing
- **Production Validation**: Post-deployment smoke tests
Generate specific test cases and implementation code for the target module.
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 · 167 lines · 0 tokens per session scan A 0db0b3961ce7
odoo-module-test 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,093 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.