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-bug-creategit 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-create)<a href="https://agentmods.dev/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-bug-create"><img src="https://agentmods.dev/badge/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-bug-create.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.01965 |
| Opus 5 | $0.00000 | $0.00983 |
| Sonnet 5 | $0.00000 | $0.00393 |
| Haiku 4.5 | $0.00000 | $0.00197 |
Grade A, and why
odoo-bug-create 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
odoo-bug-create - Initialize Odoo Module Bug Fix Workflow
Initialize a new bug fix workflow specifically for Odoo module issues, with ERP-aware tracking and resolution process.
Usage
/odoo-bug-create <module-bug-name> [description]
Examples:
/odoo-bug-create inventory-negative-stock "Inventory shows negative stock values"
/odoo-bug-create sale-discount-calculation "Sales discount not calculating correctly"
/odoo-bug-create hr-attendance-timeout "Employee attendance module login timeout"
What This Command Does
This command initializes the streamlined Odoo module bug fix workflow, designed for addressing module-specific issues with full ERP context and module dependency awareness.
Instructions
Use the @odoo-spec-task-executor agent to create Odoo module bug reports:
Initialize comprehensive Odoo module bug fix workflow with ERP context:
# 1. Workflow Overview
This is the **Odoo-specific bug fix workflow** - optimized for ERP module issues:
**Bug Fix Phases:**
1. **Report Phase** (This command) - Document the Odoo module bug
2. **Analysis Phase** (`/odoo-bug-analyze`) - Investigate with ERP context
3. **Fix Phase** (`/odoo-bug-fix`) - Implement module-aware solution
4. **Verification Phase** (`/odoo-bug-verify`) - Verify with integration testing
# 2. Module Detection and Context
Determine target module and load context:
## Module Identification
- Parse bug name to identify target module (e.g., "inventory-negative-stock" → "inventory_custom")
- Locate module path and validate existence
- Load module manifest (__manifest__.py) for dependencies
## Context Loading (Load Once - Hierarchical Context Loading)
Load complete Odoo context at the beginning:
```bash
# Load Odoo steering documents
claude-code-spec-workflow-odoo get-content ".odoo-dev/steering/business-rules.md"
claude-code-spec-workflow-odoo get-content ".odoo-dev/steering/technical-stack.md"
claude-code-spec-workflow-odoo get-content ".odoo-dev/steering/module-standards.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.
- 6d ago First seen · 269 lines · 0 tokens per session scan A 540036b35d1d
odoo-bug-create 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,965 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.
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.
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.