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-status)<a href="https://agentmods.dev/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-bug-status"><img src="https://agentmods.dev/badge/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-bug-status.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.02440 |
| Opus 5 | $0.00000 | $0.01220 |
| Sonnet 5 | $0.00000 | $0.00488 |
| Haiku 4.5 | $0.00000 | $0.00244 |
Grade A, and why
odoo-bug-status 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 — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
odoo-bug-status - Show Odoo Module Bug Status
Show current status of Odoo module bug fixes with ERP-aware context and module dependency tracking.
Usage
/odoo-bug-status [module-name] [bug-name]
Examples:
/odoo-bug-status # All module bugs status
/odoo-bug-status inventory_custom # Specific module bugs
/odoo-bug-status inventory_custom negative-stock # Specific bug status
What This Command Does
This command displays comprehensive status information for Odoo module bug fixes, including module context, business impact, and integration considerations.
Instructions
Use the @odoo-spec-task-executor agent to show Odoo module bug status:
Display comprehensive Odoo module bug status with ERP context:
# 1. Parameter Processing
Determine scope based on provided parameters:
## No parameters: All modules bug status
- Scan all detected modules for .spec/bugs/ directories
- Show summary for each module's bugs
- Highlight critical bugs requiring attention
- Display overall project bug health metrics
## Module-name only: Module-specific bug status
- Show all bugs within the specified module
- Include module dependency impact
- Display module-specific bug categories
- Show business process impact summary
## Module + bug-name: Detailed specific bug status
- Show complete workflow status for specific bug
- Include technical implementation details
- Display testing and verification progress
- Show integration impact assessment
# 2. Module Bug Discovery
Scan module structure for bug tracking:
## Module Detection
- Use existing odoo-detect functionality to find all modules
- For each module, check for .spec/bugs/ directory
- Collect bug directories and their status files
## Bug Classification
- **Active Bugs**: In progress through workflow phases
- **Resolved Bugs**: Completed verification phase
- **Blocked Bugs**: Waiting for dependencies or approval
- **Critical Bugs**: High severity impacting core operations
# 3. Status Analysis Framework
For each bug found, analyze workflow progress:
## File Presence Check
- ✅ report.md: Bug report complete
- ✅ analysis.md: Root cause analysis complete
- ✅ fix.md: Implementation details complete
- ✅ verification.md: Testing and validation complete
## Content Completeness Check
- Analyze file content quality and completeness
- Check for placeholder text or incomplete sections
- Validate against Odoo-specific requirements
- Assess business impact documentation
## Integration Impact Analysis
- Check dependencies on other modules
- Assess core Odoo integration effects
- Evaluate third-party module compatibility
- Consider upgrade path implications
# 4. Comprehensive Output Formats
## All Modules Bug Status (no parameters)
📊 Odoo Project Bug Status
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 · 312 lines · 0 tokens per session scan A 6604ccb7fee3
odoo-bug-status 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 2,440 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.
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.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.