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/xcodethink/open-claude-code-skillsWrote 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/xcodethink/open-claude-code-skills/stuck-bug)<a href="https://agentmods.dev/commands/xcodethink/open-claude-code-skills/stuck-bug"><img src="https://agentmods.dev/badge/commands/xcodethink/open-claude-code-skills/stuck-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/xcodethink/open-claude-code-skills/stuck-bug"><img src="https://agentmods.dev/badge/commands/xcodethink/open-claude-code-skills/stuck-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.00034 | $0.00291 |
| Opus 5.5 | $0.00014 | $0.00116 |
| Sonnet 5.5 | $0.00007 | $0.00058 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
stuck-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 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
stuck-bug — 反复修不好的 bug
用户输入 /stuck-bug $ARGUMENTS 触发 强制 5 步重启分析。
立刻读取并完整加载:
~/.claude/prompts/lib/02-诊断/反复修不好的bug.md
按其"行为契约"段严格执行:
- 先 git stash 之前的修复尝试(禁止在失败修复上打补丁)
- 完整读症状 → 追数据流 → 全局 grep 影响面 → 输出完整诊断 → 等用户 yes → 一次性修复
参数 $ARGUMENTS 可能含修饰符(深度思考 / 全量回归)→ 叠加 ~/.claude/prompts/modifiers/<name>.md。
核心契约:影响范围只列 1 个文件就重做第 3 步。模板正文必须完整输出注入对话,不允许总结成几句话。
参数: $ARGUMENTS
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 · 22 lines · 0 tokens per session scan A 386bedc0a975
stuck-bug is a command published in the GitHub repository xcodethink/open-claude-code-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 291 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-31.
Other commands, from other repositories
codebase-review
Review an entire codebase for architecture, engineering health, and exploitable risk; generate a prioritized remediation plan, an evidence-anchored system knowledge document, or both.
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
harness-audit
Run a deterministic repository harness audit and return a prioritized scorecard.
debug
Systematic debugging with hypotheses and evidence gathering.
verify
An embedded-device verification workflow that checks a development step through building, flashing firmware, debugging with J-Link, and reading serial logs. Firmware is software that runs directly on a microcontroller or other device.
build-fix
Incrementally fix build errors.