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/fall-out-bug/sdpWrote 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/fall-out-bug/sdp/issue)<a href="https://agentmods.dev/commands/fall-out-bug/sdp/issue"><img src="https://agentmods.dev/badge/commands/fall-out-bug/sdp/issue/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/fall-out-bug/sdp/issue"><img src="https://agentmods.dev/badge/commands/fall-out-bug/sdp/issue.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.00014 | $0.00209 |
| Opus 5.5 | $0.00006 | $0.00084 |
| Sonnet 5.5 | $0.00003 | $0.00042 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade A, and why
issue 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 1mo 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.
What it actually says
/issue — Analyze & Route Issues
When calling /issue "description":
- Load full prompt:
@.claude/skills/issue.md - Systematic debugging (5 phases):
- Symptom analysis
- Hypothesis formation
- Systematic elimination
- Root cause isolation
- Impact chain analysis
- Classify severity (P0/P1/P2/P3)
- Route to appropriate fix
- Create issue file
- Create GitHub issue (if gh available)
Quick Reference
Input: Bug description Output: Issue file + Routing recommendation
Routing:
- P0 CRITICAL →
/hotfix - P1 HIGH →
/bugfix - P2 MEDIUM → New WS
- P3 LOW → Defer
Next: /hotfix or /bugfix depending on severity
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.
- 1mo ago First seen · 34 lines · 14 tokens per session scan A 7d162091031a
issue is a command published in the GitHub repository fall-out-bug/sdp (19 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 209 once invoked, about $0.0001 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-30.
Other commands, from other repositories
refactor-clean
Refactor provided code for cleanliness, maintainability, and alignment with SOLID principles and modern best practices — no over-engineering.
lint-check
Runs linting and code quality checks. Catches style issues, potential bugs, and enforces project standards.
ui-aqa-flow-test-report-analysis
Phase 7 Test Report Analysis of ui-aqa-flow.
relationships
Explore dependencies and relationships for a file or code pattern.
test-maintenance
Maintain and evolve a Katalon True Platform/TestOps regression suite as the application changes. Use when you need to detect which tests broke or became flaky from stability and result history, diagnose whether a case needs repair vs regeneration, repair test assets (update, move, reorganize cases), refresh coverage…
tdd-bug
Fix a bug with regression test first.