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/README.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/readme)<a href="https://agentmods.dev/commands/littlebearapps/untether/readme"><img src="https://agentmods.dev/badge/commands/littlebearapps/untether/readme/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/readme"><img src="https://agentmods.dev/badge/commands/littlebearapps/untether/readme.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.00000 | $0.00824 |
| Opus 5.5 | $0.00000 | $0.00330 |
| Sonnet 5.5 | $0.00000 | $0.00165 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
README 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 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.
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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/debug companion bundle
This directory is the canonical source for each step of Untether's 8-step deep
debugging protocol. The parent command file at ../debug.md orchestrates the
steps; each file here owns the detail for one step (or one shared output).
Edit a file here to update the rule for that step everywhere — the parent command references these by path and does not duplicate their content.
Files
| File | Owns | Read before |
|---|---|---|
step-classify.md |
Step 1 — 15 Untether issue classes + diagnostic hints | Picking a class |
step-evidence.md |
Step 2 — data-source catalogue (journalctl, structlog, fleet SSH, MCP, state files) | Running any evidence command |
step-research.md |
Step 3 — docs, closed issues, upstream engine repos, library docs | Researching prior art |
systemic-patterns.md |
Step 4 — known Untether patterns + memory-aware exceptions | Scoring any signal in sweep, OR filing/escalating in targeted |
step-fix.md |
Step 7 — implementation checklist + branch model + release guard | Writing any code change |
step-verify.md |
Step 8 — post-fix verification (dev restart, integration tests, attestation, fleet rollout) | Declaring an issue verified |
output-template.md |
Output formats — Debug Report (targeted), Triage Report (sweep), Verification Spec | Emitting any user-facing report |
External references reused (not duplicated)
| Path | Purpose |
|---|---|
~/.claude/commands/monitor/severity-rubric.md |
Severity buckets and label routing |
~/.claude/commands/monitor/signal-categories.md |
Bug + enhancement signal taxonomy |
../../rules/runner-development.md |
Runner contract: 3-event sequence, session locking, signal-death handling |
../../rules/telegram-transport.md |
Outbox model, callback_data limits, ephemeral cleanup |
../../rules/control-channel.md |
PTY lifecycle, session registries, outline gate, permission modes, live sessions |
../../rules/dev-workflow.md |
Dev/staging separation — NEVER restart staging to test |
../../rules/release-discipline.md |
Branch model, integration test gate, fleet rollout |
../../rules/testing-conventions.md |
pytest patterns, stub subprocess scripts |
../../rules/help-faq.md |
FAQ touch-up checklist on releases |
../../rules/context-quality.md |
Cross-file consistency rules |
../../../docs/reference/integration-testing.md |
Per-tier integration test playbook |
../../../docs/reference/dev-instance.md |
dev vs staging service quickref |
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 6cad4e56c00d
- 1mo ago First seen · 50 lines · 0 tokens per session scan A bd9511b881b7
README is a command published in the GitHub repository littlebearapps/untether (74 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 824 tokens. 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
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.