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 skills add beettlle/pi-spine --skill spine-release-operatorgit clone --depth 1 https://github.com/beettlle/pi-spineWrote 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/beettlle/pi-spine/spine-release-operator)<a href="https://agentmods.dev/skills/beettlle/pi-spine/spine-release-operator"><img src="https://agentmods.dev/badge/skills/beettlle/pi-spine/spine-release-operator/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/beettlle/pi-spine/spine-release-operator"><img src="https://agentmods.dev/badge/skills/beettlle/pi-spine/spine-release-operator.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.00106 | $0.07415 |
| Opus 5 | $0.00053 | $0.03707 |
| Sonnet 5 | $0.00021 | $0.01483 |
| Haiku 4.5 | $0.00011 | $0.00741 |
Grade A, and why
spine-release-operator 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 10d 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 — 589 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spine Release Operator
You are the pi-spine release operator. Drive a curated release cycle from intake through publish: select work by semver profile, author/audit task packets, execute batches, verify, and bump version — with operator approval before publish.
Invoke explicitly: /skill:spine-release-operator or "run a spine release cycle for v1.5.1".
Not for executing all pending tasks — use spine-autonomous-operator for that. This skill selects a subset fitting the release profile.
Skill boundaries
| Concern | Delegate to |
|---|---|
| PROMPT/STATUS/Contract authoring | create-spine-tasks skill + templates |
| Batch land loop / recovery | spine-autonomous-operator Phase 3–4 + pi-async-orchestration.md |
| Agent shell batch policy (detached vs attached) | spine-autonomous-operator/references/agent-shell-batch-policy.md |
| Wave evidence / diagnosis tree | spine-orchestrate-waves |
| Semver scope budgets | references/release-profiles.md |
| Issue intake queries | references/issue-intake-checklist.md |
| Manifest format | references/release-manifest-template.md |
| Post-integrate regression gate | references/post-integrate-regression-gate.md |
| npm publish mechanics | docs/release/npm-publish.md |
| Upstream bug filing | references/issue-template.md |
Success criteria
- GitNexus index refreshed (
gitnexus statusup-to-date with HEAD) - Release manifest written and operator-approved
- All release-scoped tasks
.DONEand integrated onmain spine preflightgreen;npm run release:checkgreen (blocking gate) on currentmain- CI workflow green on release commit (release-safe profile — parity with
ci.yml) before tag push - Operator explicitly approved publish; version bumped and tag pushed (if approved)
- Every release-scoped
Closes #NNN/Closes: #NNNissue is CLOSED on GitHub once its fix is onmain(close after each land — do not wait for publish) - Final report with composition table, issues closed/deferred, verification output
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/issue-intake-checklist.md 3.5 KB
- references/issue-template.md 983 B
- references/pi-async-orchestration.md 3.8 KB
- references/post-integrate-regression-gate.md 4.4 KB
- references/release-manifest-template.md 4.4 KB
- references/release-profiles.md 4.2 KB
- scripts/collect-release-intake.sh 2.1 KB runs code
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.
- 10d ago First seen · 589 lines · 106 tokens per session scan A d5aee55d9561
spine-release-operator is a skill published in the GitHub repository beettlle/pi-spine (3 stars, last pushed 5d ago), licensed MIT. It adds 106 tokens to every session and 7,415 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-31.
Other skills, from other repositories
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
gsd-complete-milestone
Archive completed milestone and prepare for next version.
operating-github-cli
Default GitHub skill for the action agent. Use githubcli for any GitHub request — create/list/view/close issues and PRs, assign, labels, repos, releases, checks, github.com/owner/repo URLs, or gh api. Prefer over shellrun/!gh. Run these with githubcli in the current agent turn.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
testdino-releases
Use when the user wants to browse, inspect, create, or update releases/milestones in a TestDino project. Covers listreleases, getrelease, createrelease, and updaterelease. Accepts counter-style IDs like MS-12.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.