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/implement.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/implement)<a href="https://agentmods.dev/commands/littlebearapps/untether/implement"><img src="https://agentmods.dev/badge/commands/littlebearapps/untether/implement/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/implement"><img src="https://agentmods.dev/badge/commands/littlebearapps/untether/implement.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.00078 | $0.01605 |
| Opus 5.5 | $0.00031 | $0.00642 |
| Sonnet 5.5 | $0.00016 | $0.00321 |
| Haiku 4.5 | $0.00008 | $0.00161 |
Grade A, and why
implement 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are handling /implement. /implement executes exactly one approved
phase of a docs/plans/<slug>/ pack to a verified hand-off, then STOPS before
the PR (/pr-dev opens it). It is the build half of delivery.
User input: $ARGUMENTS
Untether adaptations (read first)
Load .claude/rules/workflow-commands.md (routing + cross-cutting rules). For
/implement:
- Authority: code + tests in the approved phase scope only, plus the one
progress-tracker.md🟡 mark. Never opens the PR. Never widens scope (→ STOP + ask). Never takes defect work (→/fix). Never runs paid work (N/A). - Release-guard. Commit to
feature/<slug>-phase-N(branch offdev). Never master/tag/release. Never--no-verify. - Dev/staging. Verify on
untether-dev; never restart staging. Neversystemctl restartfrom inside this session. - Refuse multi-phase. One phase per invocation, always.
Reuse (compose, don't re-describe)
Via the Skill tool: superpowers:executing-plans (phase discipline) +
superpowers:test-driven-development (red→green→refactor) +
superpowers:verification-before-completion (evidence before "done"). If the
phase touches a runner/schema/telegram surface, also load the matching
.claude/rules/*.md and the relevant .claude/skills/*.
Sub-commands
| Form | Action |
|---|---|
/implement <slug> <phase-N> |
Execute that phase (TDD), commit, stop before PR |
/implement <slug> |
Read-only: print the next-up phase + its pre-flight status |
/implement <slug> <phase-N> --dry-run |
Write the failing tests + stage locally; no branch push |
/implement --help |
Usage, then stop |
Flow
I-1. Gate check
- Resolve
docs/plans/<slug>/and the named phase file. If the pack or phase is missing → STOP (route to/plan). - Confirm the phase is approved and its dependencies (earlier phases) are ✅
in
progress-tracker.md. If a dependency is unmet → STOP and say which. - If more than one phase is named → refuse (one phase only).
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 aeaa7167c8b3
- 1mo ago First seen · 138 lines · 78 tokens per session scan A 83e3ddb209e4
implement is a command published in the GitHub repository littlebearapps/untether (74 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 1,605 once invoked, about $0.0003 per session on Opus 5.5. 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
publish
Publish oh-my-opencode to npm via GitHub Actions workflow.
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits.
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer.
voiceover
Start a feature the demo-driven way — approve the voice-over (instead of a PRD), build on a fresh worktree, ship a PR with the proof on it.
release
Run the iPolloWork release flow.
release
Verify, write the CHANGELOG, cut a version — then hand the release sequence back.