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/skills/release-coordination/SKILL.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/skills/littlebearapps/untether/release-coordination)<a href="https://agentmods.dev/skills/littlebearapps/untether/release-coordination"><img src="https://agentmods.dev/badge/skills/littlebearapps/untether/release-coordination/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/skills/littlebearapps/untether/release-coordination"><img src="https://agentmods.dev/badge/skills/littlebearapps/untether/release-coordination.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 249 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
- high Tool Misuse · line 267 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 271 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Rogue Agent · line 254 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00041 | $0.05387 |
| Opus 5.5 | $0.00016 | $0.02155 |
| Sonnet 5.5 | $0.00008 | $0.01077 |
| Haiku 4.5 | $0.00004 | $0.00539 |
Grade A, and why
release-coordination 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 — 465 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Coordination
Step-by-step release workflow for Untether. Covers the full lifecycle from issue audit through PyPI publishing and post-release verification.
Key files
| File | Purpose |
|---|---|
pyproject.toml |
Package version (version = "X.Y.Z") |
CHANGELOG.md |
Release notes with issue links |
uv.lock |
Locked dependency versions |
.github/workflows/release.yml |
Tag-triggered PyPI publish (OIDC trusted publishing; no reviewer gate — the release merge is the approval, see Phase 7) |
.github/workflows/ci.yml |
PR/push CI (format, lint, ty, pytest, build, install-test, lockfile, pip-audit, bandit, docs, testpypi-publish, release-validation) |
.github/workflows/prerelease-deps.yml |
Weekly pre-release dependency testing (informational) |
scripts/validate_release.py |
Automated changelog/version validation (runs in CI on version-bump PRs) |
scripts/healthcheck.sh |
Post-deploy health check (systemd, version, logs, Bot API) |
scripts/staging.sh |
Staging install helper (TestPyPI rc install, rollback, status) |
cliff.toml |
git-cliff config for changelog drafting from conventional commits |
.claude/rules/release-discipline.md |
Auto-loaded rule enforcing issue/changelog discipline |
Release workflow phases
1. Issue audit → 2. Version decision → 3. Changelog → 4. Validate →
5. Integration test → 5.5. Attestation marker → 6. Staging (lba-1) +
fleet rollout → 7. Tag & publish
Work happens on feature/* / fix/* branches → PR → dev (rc → TestPyPI) → PR dev→master. The PyPI release pipeline (release.yml) triggers on the v* tag that auto-tag-on-master.yml creates when a stable version is merged to master (by Nathan, or by Claude via /pr-main X.Y.Z --merge after his explicit approval).
Phase 5.5 (attestation) is the gate that makes the fleet rollout safe.
Without it, scripts/fleet-rollout.sh refuses to upgrade production hosts.
Phase 6 (staging + fleet rollout) parallelises across all 5 hosts —
lba-1 staging, nsd, channelo, sl, mac — instead of staging on lba-1 alone.
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 21a68f025fb3
- 1mo ago First seen · 460 lines · 41 tokens per session scan A 06ba2229d68f
release-coordination is a skill published in the GitHub repository littlebearapps/untether (74 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 5,387 once invoked, about $0.0002 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 skills, from other repositories
release
Generic release assistant — analyzes repo release rules, caches them in .omc/RELEASERULE.md, then guides the release.
publish
Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts. Ship-only: never runs pre-publish-review or re-reviews merged code unless the user explicitly asks. Argument: . Triggers: publish, release, deploy, npm publish.
pre-publish-review
Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release…
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer. Triggers: unpublished changes, changelog, what changed, whats new.
cmux-release
Prefer the /release command. It determines the new version (minor by default), gathers the Changelog line from each PR merged since the last stable tag, updates CHANGELOG.md, runs ./scripts/bump-version.sh, commits, runs ./scripts/release-pretag-guard.sh, then tags and pushes.
gh-cli
Patterns for invoking the GitHub CLI (gh v2.100.0+) from agents. Use when the task mentions GitHub, gh, pull requests/PRs, issues, releases, gists, Actions/workflow runs, forks, repo cloning, reviews, or you need exact gh commands. Covers pagination, repo targeting, search vs list, discussions, projects, rulesets…