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-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/bug-create)<a href="https://agentmods.dev/commands/stanleykao72/claude-code-spec-workflow-odoo/bug-create"><img src="https://agentmods.dev/badge/commands/stanleykao72/claude-code-spec-workflow-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 | $0.00000 | $0.00680 |
| Opus 5 | $0.00000 | $0.00340 |
| Sonnet 5 | $0.00000 | $0.00136 |
| Haiku 4.5 | $0.00000 | $0.00068 |
Grade A, and why
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 4d 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-create — 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Create Command
Initialize a new bug fix workflow for tracking and resolving bugs.
Usage
/bug-create <bug-name> [description]
Workflow Overview
This is the streamlined bug fix workflow - a lighter alternative to the full spec workflow for addressing bugs and issues.
Bug Fix Phases
- Report Phase (This command) - Document the bug
- Analysis Phase (
/bug-analyze) - Investigate root cause - Fix Phase (
/bug-fix) - Implement solution - Verification Phase (
/bug-verify) - Confirm resolution
Instructions
You are helping create a new bug fix workflow. This is designed for smaller fixes that don't need the full spec workflow overhead.
-
Create Directory Structure
- Create
.claude/bugs/{bug-name}/directory - Initialize report.md, analysis.md, and verification.md files
- Create
-
Load ALL Context Once (Hierarchical Context Loading) Load complete context at the beginning for the bug creation process:
# Load steering documents (if available) claude-code-spec-workflow get-steering-context # Load bug templates claude-code-spec-workflow get-template-context bug -
Gather Bug Information
- Take the bug name and optional description
- Guide user through bug report creation
- Use structured format for consistency
-
Generate Bug Report
- Template to Follow: Use the bug report template from the pre-loaded context above (do not reload)
- Create detailed bug description following the bug report template structure
Template Usage
- Follow exact structure: Use loaded bug report template precisely
- Include all sections: Don't omit any required template sections
- Structured format: Follow the template's format for consistency
-
Request User Input
- Ask for bug details if not provided in description
- Guide through each section of the bug report
- Ensure all required information is captured
-
Save and Proceed
- Save the completed bug report to report.md
- Ask: "Is this bug report accurate? If so, we can move on to the analysis."
- Wait for explicit approval before proceeding
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.
- 4d ago First seen · 92 lines · 0 tokens per session scan A d757c6b98b41
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 680 tokens. A static security scan graded it A with 0 findings. It is 100% identical to bug-create, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.