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/step-fixgit 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.01732 |
| Opus 5 | $0.00000 | $0.00866 |
| Sonnet 5 | $0.00000 | $0.00346 |
| Haiku 4.5 | $0.00000 | $0.00173 |
Grade A, and why
step-fix 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Step 7 — Fix with verification criteria
Implement the minimal fix. Document a verification spec. Apply
needs-verification. Do not close the issue.
This file expands the parent command's Step 7 summary. Read both — the parent file is the orchestration; this file is the canonical checklist.
Hard release-guard rules (read first)
From .claude/rules/release-discipline.md and .claude/rules/dev-workflow.md:
- NEVER push to master. Hooks block; do not work around.
git push origin masteris blocked. - NEVER create tags.
git tag v*is blocked.auto-tag-on-master.ymlcreates tags from stable PR merges. - NEVER merge PRs to master.
gh pr mergeto master is blocked. - NEVER run
gh release create. Release publishing is automated. - NEVER use
--no-verify,--no-gpg-sign, or any hook-skip flag. Hooks block guard-script edits too. - NEVER restart
untether.service(staging) to test code changes. Restartuntether-dev.serviceinstead. Restarting staging during dev is always wrong (seedev-workflow.md). - NEVER edit guard scripts or
.claude/hooks.json.release-guard-protect.shblocks these. Only Nathan changes them outside Claude Code.
The release pipeline is single-gate: dev push → TestPyPI; Nathan
squash-merges a stable version PR to master → auto-tag → release.yml
publishes to PyPI. The master PR review IS the release approval.
The 7-step implementation checklist
1. Branch off dev
git fetch origin
git checkout dev
git pull --ff-only origin dev
git checkout -b "fix/<issue-N>-<short-slug>"
Branch naming: fix/<N>-<slug> for bugs, feature/<slug> for features.
2. Implement the minimal fix
Edit only the files needed. Don't add comments, don't refactor surrounding code, don't add backwards-compat shims. If the fix is one line, the diff should be one line.
Follow the area's rule file:
- runner-* changes →
runner-development.md(3-event contract, session locking, signal-death handling, EventFactory). - telegram-* changes →
telegram-transport.md(outbox-only writes, 64-byte callback, ephemeral cleanup). - control-channel changes →
control-channel.md(PTY lifecycle, registry cleanup, cooldown). - runner edits trigger
.claude/hooks/runner-edit-context.sh; telegram edits triggertelegram-edit-context.sh— these print contract reminders.
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 · 188 lines · 0 tokens per session scan A 802830c5a43c
step-fix 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 1,732 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.