Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/qwickapps/ai-sdlc-workflowsnpx agentmods add commands/qwickapps/ai-sdlc-workflows/bugWrote 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/qwickapps/ai-sdlc-workflows/bug)<a href="https://agentmods.dev/commands/qwickapps/ai-sdlc-workflows/bug"><img src="https://agentmods.dev/badge/commands/qwickapps/ai-sdlc-workflows/bug/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/qwickapps/ai-sdlc-workflows/bug"><img src="https://agentmods.dev/badge/commands/qwickapps/ai-sdlc-workflows/bug.svg" alt="Reviewed on agentmods" width="80" 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.00009 | $0.01944 |
| Opus 5.5 | $0.00004 | $0.00778 |
| Sonnet 5.5 | $0.00002 | $0.00389 |
| Haiku 4.5 | $0.00001 | $0.00194 |
Grade A, and why
bug 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 2mo 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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Fix Workflow
You are now in Bug Fix Mode. Follow this workflow strictly.
Input: $ARGUMENTS (bug description, error message, issue number, or reproduction steps)
CRITICAL RULES
- Understand before fixing - investigate root cause first (see RESEARCH-DEPTH.md)
- NEVER auto-commit - always wait for explicit user approval
- NEVER add legacy support or workarounds - fix the actual issue
- No attributions in commit messages
- When blocked - STOP and discuss (see COMMUNICATION-PROTOCOL.md)
- Validate thoroughly - build, test, E2E (see VALIDATION-GATES.md)
- Use worktree script - NEVER use git commands directly (see WORKTREE-ENFORCEMENT.md)
Interactive Setup
Check if $ARGUMENTS is provided.
If $ARGUMENTS is empty or unclear, ask:
"What bug would you like me to investigate? Please provide:
- Error message or unexpected behavior
- Steps to reproduce (if known)
- Expected vs actual behavior
- Issue/ticket number (GitHub issue, JIRA ticket, etc.)"
Extract and store the issue/ticket number from the response for:
- Branch naming (bugfix/ISSUE-123)
- Document attachment
- Commit messages
Wait for response before proceeding.
Workflow Phases
PHASE 1: Investigation (Quality Engineer + Coder)
Research Requirements: Follow RESEARCH-DEPTH.md guidelines:
- Use Explore agent for unfamiliar code areas
- Use Grep for specific code patterns
- Use Chrome automation to verify frontend bugs
- Use QwickBrain MCP to check for similar past bugs
- Gather evidence with file:line references
- No assumptions without verification
-
Reproduce the bug:
- Understand the expected vs actual behavior
- Identify steps to reproduce
- Ask clarifying questions if unclear
-
Root cause analysis:
- Use Explore agent to understand affected system
- Use Grep to find relevant code
- Read actual code, don't assume behavior
- Trace execution path
- Identify the source of the bug
- Document findings with file:line evidence
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.
- 2mo ago First seen · 267 lines · 9 tokens per session scan A 1b463ba6c91b
bug is a command published in the GitHub repository qwickapps/ai-sdlc-workflows (2 stars, last pushed 7mo ago), licensed MIT. It adds 9 tokens to every session and 1,944 once invoked, about $0.0000 per session on Opus 5.5. 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-31.
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…
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.
react-native
Command "react-native" from getsentry/toolkit, covering xcode build step (react-native xcode) and important notes.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
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…
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.