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-bug-analyze)<a href="https://agentmods.dev/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-bug-analyze"><img src="https://agentmods.dev/badge/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-bug-analyze.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.01827 |
| Opus 5 | $0.00000 | $0.00914 |
| Sonnet 5 | $0.00000 | $0.00365 |
| Haiku 4.5 | $0.00000 | $0.00183 |
Grade A, and why
odoo-bug-analyze 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
odoo-bug-analyze - Analyze Odoo Module Bug Root Cause
Investigate and analyze the root cause of a reported Odoo module bug with ERP-specific context.
Usage
/odoo-bug-analyze [module-bug-name]
What This Command Does
This command performs deep analysis of Odoo module bugs, considering ERP-specific patterns, module dependencies, and Odoo framework constraints to identify root causes and plan effective solutions.
Instructions
Use the @odoo-spec-task-executor agent to analyze Odoo module bugs:
Perform comprehensive Odoo module bug analysis with ERP-specific context:
# 1. Prerequisites and Context Loading
Load complete Odoo development context:
## Odoo Project Context
- Load .odoo-dev/config.json for project configuration
- Load .odoo-dev/steering/ documents:
* business-rules.md: ERP business logic and workflow standards
* technical-stack.md: Odoo technical guidelines and patterns
* module-standards.md: Custom module development standards
## Module Context
- Identify target module from bug name
- Load module manifest (__manifest__.py) and dependencies
- Understand module's role in the ERP ecosystem
- Check module's Odoo version compatibility
## Bug Report Context
- Load existing bug report from [module-path]/.spec/bugs/[bug-name]/report.md
- Understand reported symptoms and reproduction steps
- Review user impact and business process affected
# 2. Odoo-Specific Investigation Process
## Module Architecture Analysis
Investigate with Odoo ERP context:
- **Model Inheritance Chains**: Check _inherit and _inherits relationships
- **View Hierarchy**: Analyze view inheritance and customizations
- **Security Rules**: Review record rules and access control
- **Data Flow**: Trace data through Odoo ORM and business logic
- **Integration Points**: Check API calls, web controllers, and external integrations
## ERP Pattern Analysis
- **Business Logic Validation**: Check compute methods, constraints, and onchange
- **Workflow Integration**: Analyze state transitions and approval processes
- **Multi-company Impact**: Consider multi-tenancy and data isolation
- **Localization Effects**: Check currency, language, and regional settings
- **Performance Implications**: Analyze database queries and bulk operations
## Odoo Framework Considerations
- **ORM Usage**: Check for proper use of Odoo ORM methods
- **Transaction Handling**: Analyze commit/rollback patterns
- **Caching Issues**: Check for cache invalidation problems
- **Module Load Order**: Verify dependency loading sequence
- **API Compatibility**: Check for deprecated method usage
# 3. Root Cause Investigation
## Technical Root Cause Analysis
Focus on Odoo-specific failure patterns:
- **Inheritance Conflicts**: Multiple modules modifying same functionality
- **Database Schema Issues**: Field conflicts, constraint violations
- **Security Rule Conflicts**: Overlapping or contradicting access rules
- **View Rendering Problems**: Template inheritance and XML conflicts
- **Business Logic Errors**: Incorrect compute methods or domain filters
## Integration Impact Analysis
- **Dependent Module Effects**: How does this bug affect other modules?
- **Core Odoo Integration**: Does this conflict with standard Odoo behavior?
- **Third-party Module Compatibility**: Conflicts with community/enterprise modules
- **Upgrade Path Impact**: Will this affect future Odoo version upgrades?
## Business Process Impact
- **Workflow Disruption**: Which business processes are affected?
- **Data Integrity**: Is there risk of data corruption or loss?
- **User Experience**: How does this affect end-user operations?
- **Reporting Impact**: Does this affect business intelligence or reporting?
# 4. Solution Strategy Planning
## Fix Approach Design
Plan Odoo-appropriate solutions:
- **Inheritance Strategy**: Use proper _inherit patterns to avoid conflicts
- **Override vs Extension**: Determine whether to override or extend functionality
- **Migration Considerations**: Plan for future Odoo version compatibility
- **Testing Strategy**: Plan pytest-odoo integration and coverage
## Risk Assessment
- **Module Stability**: Impact on existing module functionality
- **Data Migration**: Need for data updates or corrections
- **Performance Impact**: Query performance and resource usage
- **Deployment Considerations**: Production deployment strategy
# 5. Create Analysis Document
Create comprehensive analysis in [module-path]/.spec/bugs/[bug-name]/analysis.md:
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 · 240 lines · 0 tokens per session scan A dce5717ddcfc
odoo-bug-analyze 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,827 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
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.