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.
npx agentmods add commands/littlebearapps/untether/readmegit clone --depth 1 https://github.com/littlebearapps/untetherWhat 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 | $0.00000 | $0.00821 |
| Opus 5 | $0.00000 | $0.00411 |
| Sonnet 5 | $0.00000 | $0.00164 |
| 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 2d 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, cooldown, ask-question flow |
../../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.
- 2d ago First seen · 50 lines · 0 tokens per session scan A bd9511b881b7
README is a command published in the GitHub repository littlebearapps/untether (66 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 821 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
psm
/oh-my-claudecode:psm is a compatibility alias for /oh-my-claudecode:project-session-manager.
plan-review
The core plan review flow across Claude Code, Codex, and other supported agent hosts.
release
Ship a stable cmux release built by CI: bump version, update changelog, open a PR, merge, tag, then GitHub Actions builds, signs, and publishes.
refresh-compare-pages
Freshly research, add, and refresh marketing compare pages, then open a descriptive PR.
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.
self-improve
This compatibility command keeps /oh-my-claudecode:self-improve available without loading the full self-improve skill description in every Claude Code session.