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/step-fix.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/step-fix)<a href="https://agentmods.dev/commands/littlebearapps/untether/step-fix"><img src="https://agentmods.dev/badge/commands/littlebearapps/untether/step-fix/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/step-fix"><img src="https://agentmods.dev/badge/commands/littlebearapps/untether/step-fix.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.01879 |
| Opus 5.5 | $0.00000 | $0.00752 |
| Sonnet 5.5 | $0.00000 | $0.00376 |
| Haiku 4.5 | $0.00000 | $0.00188 |
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 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 — 193 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 from a fix. Only
/pr-main X.Y.Z --mergedoes, after Nathan approves the release (the guard asks him to confirm). - 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/settings.json. Only Nathan changes them outside Claude Code. The guard blocks Edit/Write on them; never work around a block.
The release pipeline is single-gate: dev push → TestPyPI; a stable version
PR squash-merged to master (by Nathan, or by /pr-main --merge on his
explicit go) → auto-tag → release.yml publishes to PyPI. Nathan's approval IS
the release gate.
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.
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 · +5 lines 5b4ddf6cd24c
- 1mo ago First seen · 188 lines · 0 tokens per session scan A 802830c5a43c
step-fix 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 1,879 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.