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 skills/littlebearapps/untether/release-coordinationnpx skills add littlebearapps/untether --skill release-coordinationgit 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.svg" alt="Measured on agentmods" 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 | $0.00041 | $0.04766 |
| Opus 5 | $0.00020 | $0.02383 |
| Sonnet 5 | $0.00008 | $0.00953 |
| Haiku 4.5 | $0.00004 | $0.00477 |
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 3d 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 — 460 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, reviewer approval gate) |
.github/workflows/ci.yml |
PR/push CI (format, lint, ty, pytest, build, lockfile, audit, bandit, docs, testpypi, 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
All seven (now-8) phases happen in a single branch (typically master for patches, feature/* for minors). The CI release pipeline triggers on v* tags pushed to master.
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.
Phase 1: Issue audit
Find commits since the last release that lack GitHub issues.
# Find the last release tag
LAST_TAG=$(git describe --tags --abbrev=0)
# List commits since last tag
git log --oneline "$LAST_TAG"..HEAD
# List open issues
direnv exec . gh issue list --state open
# List recently closed issues
direnv exec . gh issue list --state closed --limit 20
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.
- 3d ago First seen · 460 lines · 41 tokens per session scan A 06ba2229d68f
release-coordination is a skill published in the GitHub repository littlebearapps/untether (66 stars, last pushed 4d ago), licensed MIT. It adds 41 tokens to every session and 4,766 once invoked, about $0.0002 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 skills, from other repositories
release-plannotator
Prepare and execute a Plannotator release — draft release notes with full contributor credit, bump versions across all package files, build in dependency order, and kick off the tag-driven release pipeline. Use this skill whenever the user mentions preparing a release, bumping versions, writing release notes, tagging…
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 16-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 (5 agents) for holistic review, and 1 oracle for overall release synthesis. Runs ONLY when the user…
work-with-pr
Full PR lifecycle in a fresh task-owned git worktree: implement via the ulw-loop skill with mandatory evidence-bound manual QA → reviewer-readable English PR → verification loop (CI + Cubic, where Cubic is skipped only when its quota is exhausted) → merge by default → worktree cleanup. Decomposes one task into the…
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 commits since the last tag, updates CHANGELOG.md, runs ./scripts/bump-version.sh, commits, runs ./scripts/release-pretag-guard.sh, then tags and pushes.