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/pr-maingit 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.00099 | $0.01807 |
| Opus 5 | $0.00049 | $0.00903 |
| Sonnet 5 | $0.00020 | $0.00361 |
| Haiku 4.5 | $0.00010 | $0.00181 |
Grade A, and why
pr-main 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are handling /pr-main. /pr-main prepares a stable release and opens
the dev→master PR — then STOPS. Merging that PR is Nathan's single release
gate (→ auto-tag-on-master.yml → release.yml → PyPI). /pr-main does
everything Claude is allowed to do and hard-stops at the operator boundary.
User input: $ARGUMENTS
Untether adaptations (read first)
Load .claude/rules/workflow-commands.md (routing + cross-cutting rules) and
.claude/rules/release-discipline.md (semver, changelog format, FAQ, staging vs
release). Key points:
- Authority boundary (verified against
release-guard.sh).gh pr create --base masteris allowed (creating a PR is not a push/merge/tag/release).gh pr mergeto master,git push master,git tag v*, andgh release createare blocked. So/pr-mainmay OPEN the release PR but may never merge/tag/release it — and it must not try (don't fight the guard). - The version-bump commit lands on
dev(pushing todevis allowed;masteris not). The PR isdev→master. fleet-rollout.shis the operator's step —/pr-mainnever runs it. The attestation marker is surfaced as advisory context in the PR body only.- Confirm-gated + idempotent. Surface the PR title + body and wait for a tap;
a re-invoked
/pr-mainmust not double-open the release PR (check for an existing opendev→masterPR first). - Untether-mode. State the confirmation in text and STOP for a reply. Keep the report brief.
Sub-commands
| Form | Action |
|---|---|
/pr-main X.Y.Z |
Prepare the stable release + open the dev→master PR, then STOP |
/pr-main X.Y.Z --dry-run |
Prepare + validate + print the would-be PR body; open nothing |
/pr-main --rc-summary |
Collapse the rc CHANGELOG sections + validate only; no bump, no PR |
/pr-main --help |
Usage, then stop |
Flow
M-1. Confirm the release is cuttable
git fetchand confirmdevis green + ahead ofmaster(CI ondevis the last TestPyPI publish).- Confirm the intended stable
X.Y.Zis decided and is a proper stable version (norc/a/b/devsuffix — those are skipped byauto-tag-on-master.yml). - If an open
dev→masterPR already exists for this version → STOP (idempotent; don't double-open).
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 · 136 lines · 99 tokens per session scan A d5381771150b
pr-main is a command published in the GitHub repository littlebearapps/untether (66 stars, last pushed 3d ago), licensed MIT. It adds 99 tokens to every session and 1,807 once invoked, about $0.0005 per session on Opus 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
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.