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/pr-dev.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/pr-dev)<a href="https://agentmods.dev/commands/littlebearapps/untether/pr-dev"><img src="https://agentmods.dev/badge/commands/littlebearapps/untether/pr-dev/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/pr-dev"><img src="https://agentmods.dev/badge/commands/littlebearapps/untether/pr-dev.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.00104 | $0.02105 |
| Opus 5.5 | $0.00042 | $0.00842 |
| Sonnet 5.5 | $0.00021 | $0.00421 |
| Haiku 4.5 | $0.00010 | $0.00211 |
Grade A, and why
pr-dev 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are handling /pr-dev. /pr-dev takes a feature/fix/chore branch from
"code + tests done" to ONE merge-ready PR to dev (→ TestPyPI on merge). Docs
reconciliation is a completion criterion here, not a separate /docs stage.
This is the everyday delivery command and Untether's batch-PR unit.
User input: $ARGUMENTS
Untether adaptations (read first)
Load .claude/rules/workflow-commands.md (routing + cross-cutting rules) and
.claude/rules/release-discipline.md (changelog/version/FAQ discipline). Key
points:
- Release-guard obedience. PR to
devonly.gh pr merge --squashis allowed only with base =dev(the only merge/pr-devmay do; the release merge is/pr-main X.Y.Z --mergeonly). Never push/merge tomaster, nevergit tag, nevergh release create, never--no-verify. The ruleset blocks directmasterpushes; the local guard (#915/#917) gatesmastermerges — never work around a block. - Dev/staging separation. Never
systemctl restartstaging or dev from inside this session (hot-reload drain drops the final message). - Confirm-gated + idempotent. Surface the drafted PR body and wait for a tap;
de-dupe against an existing open PR for this branch; a re-invoked
/pr-devmust not double-open or double-merge. - Redaction. Scrub tokens/keys/env/chat-content/fleet identifiers from any evidence quoted in the PR body.
- Untether-mode.
--mergeconfirmation is stated in text and STOPS for a reply. Keep the report brief.
Sub-commands
| Form | Action |
|---|---|
/pr-dev (no args) |
Finalise the current branch → open a PR to dev (stops merge-ready) |
/pr-dev --rc X.Y.ZrcN |
Bump pyproject.toml + uv lock to the rc (chore(release): X.Y.ZrcN, or fold it into the batch PR titled rcN: … — X.Y.ZrcN (#…)) → PR to dev |
/pr-dev --dry-run |
Gate + local checks + print what would happen; open/push nothing |
/pr-dev --merge |
Squash-merge the PR to dev only (confirm-gated) → TestPyPI CI |
/pr-dev --help |
Usage, then stop |
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 · +4 lines · +46 tokens per session 7cb8f7813d00
- 1mo ago First seen · 145 lines · 58 tokens per session scan A 8cd5f41af556
pr-dev is a command published in the GitHub repository littlebearapps/untether (74 stars, last pushed today), licensed MIT. It adds 104 tokens to every session and 2,105 once invoked, about $0.0004 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.