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-orchestrate-wavesgit 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-orchestrate-waves)<a href="https://agentmods.dev/skills/beettlle/pi-spine/spine-orchestrate-waves"><img src="https://agentmods.dev/badge/skills/beettlle/pi-spine/spine-orchestrate-waves/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-orchestrate-waves"><img src="https://agentmods.dev/badge/skills/beettlle/pi-spine/spine-orchestrate-waves.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.00085 | $0.03054 |
| Opus 5 | $0.00043 | $0.01527 |
| Sonnet 5 | $0.00017 | $0.00611 |
| Haiku 4.5 | $0.00009 | $0.00305 |
Grade A, and why
spine-orchestrate-waves 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spine Orchestrate Waves
Drive multi-wave spine development from an external agent session. Spine owns batch execution, review, contract verify, and integrate gates; you (the agent) own wave selection, spine wait, evidence review, gate approve, integrate decisions, retry/dismiss, and conflict resolution.
Gate approval by the external agent is intentional — workers receive not_supported from spine_request_gate (FR-SHIP-13). Do not expect workers to approve integrate gates.
Invoke explicitly: /skill:spine-orchestrate-waves, /spine-orchestrate pending, or "orchestrate all pending spine waves."
Not for authoring task packets — use create-spine-tasks. Not for curated semver releases — use spine-release-operator.
Skill boundaries
| Concern | Delegate to |
|---|---|
| Task packet authoring | create-spine-tasks skill |
| Curated release subset | spine-release-operator skill |
| Agent shell batch policy (detached vs attached) | spine-autonomous-operator/references/agent-shell-batch-policy.md |
| Pi async batch/verify (MonitorCreate) | spine-release-operator/references/pi-async-orchestration.md |
| Post-integrate regression gate | spine-release-operator/references/post-integrate-regression-gate.md |
| Canonical how-to prose | references/outer-loop.md (synced from docs/adoption/agent-orchestrated-waves.md) |
Slash entry (/spine-orchestrate) |
pi-spine extension — wave plan + outer loop checklist |
| Single-task suggested command | /spine-next inside land loop |
Prerequisites
- pi-spine installed (
pi install npm:pi-spineor local link) .spine/spine-config.jsonpresent (spine initif missing)- Tasks decomposed into waves (
spine plan pendingshows wave structure) - Familiarity with operator-runbook §4 land loop
What ships with it
1 file 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.
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 · 217 lines · 85 tokens per session scan A b2fe8d4e4bc3
spine-orchestrate-waves is a skill published in the GitHub repository beettlle/pi-spine (3 stars, last pushed 5d ago), licensed MIT. It adds 85 tokens to every session and 3,054 once invoked, about $0.0004 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.