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/bug-analyzegit 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/bug-analyze)<a href="https://agentmods.dev/commands/stanleykao72/claude-code-spec-workflow-odoo/bug-analyze"><img src="https://agentmods.dev/badge/commands/stanleykao72/claude-code-spec-workflow-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.00870 |
| Opus 5 | $0.00000 | $0.00435 |
| Sonnet 5 | $0.00000 | $0.00174 |
| Haiku 4.5 | $0.00000 | $0.00087 |
Grade A, and why
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 5d 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.
This is a copy
100% identical to bug-analyze — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Analyze Command
Investigate and analyze the root cause of a reported bug.
Usage
/bug-analyze [bug-name]
Phase Overview
Your Role: Investigate the bug and identify the root cause
This is Phase 2 of the bug fix workflow. Your goal is to understand why the bug is happening and plan the fix approach.
Instructions
Manual Analysis Process:
-
Prerequisites
- Ensure report.md exists and is complete
- Load the bug report for context
- Load steering documents:
# Windows: claude-code-spec-workflow get-content "C:\path\to\project\.claude\steering\tech.md" claude-code-spec-workflow get-content "C:\path\to\project\.claude\steering\structure.md" # macOS/Linux: claude-code-spec-workflow get-content "/path/to/project/.claude/steering/tech.md" claude-code-spec-workflow get-content "/path/to/project/.claude/steering/structure.md" - Understand the reported issue completely
-
Investigation Process
-
Code Investigation
- Search codebase for relevant functionality
- Identify files, functions, and components involved
- Map data flow and identify potential failure points
- Look for similar issues or patterns
-
Root Cause Analysis
- Determine the underlying cause of the bug
- Identify contributing factors
- Understand why existing tests didn't catch this
- Assess impact and risks
-
Solution Planning
- Design fix strategy
- Consider alternative approaches
- Plan testing approach
- Identify potential risks
-
-
Create Analysis Document
- Template to Follow: Use the bug analysis template from the pre-loaded context above (do not reload)
- Read and follow: Use the bug analysis template and follow all sections precisely
- Document investigation findings following the template structure
Template Usage
- Follow exact structure: Use
.claude/templates/bug-analysis-template.mdprecisely - Include all sections: Don't omit any required template sections
- Detailed analysis: Follow the template's format for comprehensive investigation
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.
- 5d ago First seen · 107 lines · 0 tokens per session scan A af137dcae329
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 870 tokens. A static security scan graded it A with 0 findings. It is 100% identical to bug-analyze, differing in 0 lines, and is treated as a copy.
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.