Borrowing it
Nothing to install: this file belongs to littlebearapps/untether. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/littlebearapps/untether/master/.claude/commands/debug.mdgit clone --depth 1 https://github.com/littlebearapps/untetherWrote 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/littlebearapps/untether/debug)<a href="https://agentmods.dev/commands/littlebearapps/untether/debug"><img src="https://agentmods.dev/badge/commands/littlebearapps/untether/debug/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/littlebearapps/untether/debug"><img src="https://agentmods.dev/badge/commands/littlebearapps/untether/debug.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.00037 | $0.04233 |
| Opus 5.5 | $0.00015 | $0.01693 |
| Sonnet 5.5 | $0.00007 | $0.00847 |
| Haiku 4.5 | $0.00004 | $0.00423 |
Grade A, and why
debug scanned grade A with 1 finding 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 18d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
(e.g. `event=subprocess.liveness_stall`) and time window. How it starts
The opening of the file, as written. The whole thing — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are handling the user's /debug request. /debug is Untether's 8-step deep
debugging protocol. It runs in one of two modes — general sweep (ranked
triage report across fleet logs + open issues, no auto-filing) or targeted
(full 8-step rigor per named GitHub issue, posted as an issue comment with a
verification spec).
User input: $ARGUMENTS
This command is project-scoped to Untether. It is not the generic
/debug <issue> shipped in the user's global ~/.claude/commands/debug.md;
project commands take precedence when invoked from inside /home/nathan/untether.
Companion files (canonical references)
| File | Step covered | Purpose |
|---|---|---|
.claude/commands/debug/README.md |
n/a | How the bundle fits together |
.claude/commands/debug/step-classify.md |
Step 1 | 15 Untether issue classes + diagnostic hints |
.claude/commands/debug/step-evidence.md |
Step 2 | Data-source catalogue (journalctl, structlog, fleet SSH, MCP, state files) |
.claude/commands/debug/step-research.md |
Step 3 | Docs, closed issues, upstream engine repos, library docs |
.claude/commands/debug/systemic-patterns.md |
Step 4 | ~20 known Untether patterns + memory-aware exceptions |
.claude/commands/debug/step-fix.md |
Step 7 | Implementation checklist (tests, lint, format, changelog, branch model) |
.claude/commands/debug/step-verify.md |
Step 8 | Post-fix verification (dev restart, integration tests, attestation, fleet rollout) |
.claude/commands/debug/output-template.md |
output | Debug-report-comment and triage-report templates |
~/.claude/commands/monitor/severity-rubric.md |
(reused) | Severity buckets and label routing — single source of truth |
~/.claude/commands/monitor/signal-categories.md |
(reused) | Bug/enhancement signal taxonomy |
Read the relevant companion file BEFORE executing each step. Do not duplicate their content here — they are the canonical source.
Sub-commands
| Form | Action |
|---|---|
/debug (no args) |
General sweep, default window = 24 hours |
/debug sweep [hours] |
General sweep, custom window |
/debug <issue_number> [more numbers...] |
Targeted: full 8-step per issue |
/debug --issue <n> |
Targeted: single issue (explicit form) |
/debug --help |
Print usage block |
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.
- 18d ago Changed · +1 lines b3868e6d6925
- 1mo ago First seen · 327 lines · 37 tokens per session scan A 678d419cb02d
debug is a command published in the GitHub repository littlebearapps/untether (74 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 4,233 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
root-cause
Use when any test fails, bug appears, or behaviour surprises you, before proposing a fix - find the cause and prove it, by reading real evidence, tracing bad values back to their origin, comparing against a working case, and testing one hypothesis at a time.
refactor
Refactor and optimize [code].
hotfix
Emergency fix workflow with audit trail.
kotlin-build
Fix Kotlin/Gradle build errors, compiler warnings, and dependency issues incrementally. Invokes the kotlin-build-resolver agent for minimal, surgical fixes.
bug-report
Create structured bug report.
wtfp:report-bug
Collect a reproducible bug report and publish it only after explicit user approval.