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 create-spine-tasksgit 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/create-spine-tasks)<a href="https://agentmods.dev/skills/beettlle/pi-spine/create-spine-tasks"><img src="https://agentmods.dev/badge/skills/beettlle/pi-spine/create-spine-tasks/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/create-spine-tasks"><img src="https://agentmods.dev/badge/skills/beettlle/pi-spine/create-spine-tasks.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.00082 | $0.09765 |
| Opus 5 | $0.00041 | $0.04882 |
| Sonnet 5 | $0.00016 | $0.01953 |
| Haiku 4.5 | $0.00008 | $0.00976 |
Grade A, and why
create-spine-tasks 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 — 612 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Spine Tasks
Creates structured task packets (PROMPT.md + STATUS.md) for autonomous execution via pi-spine (spine batch start, /spine). The spine engine handles waves, worktree lanes, checkpoint discipline, cross-model review, integrate gates, and the dashboard — so PROMPT.md stays focused on what to build, not how the orchestrator runs.
Works from a local pi-spine checkout (pi install /path/to/pi-spine -l) or after pi install npm:pi-spine.
Architecture
PRD / brief
│
├─ Lean authoring ─────────────────────────────────────────────┐
│ Step 0? → Step A → Step B → Step C │
│ │
└─ Full authoring ───────────────────────────────────────────┤
Step 0? → A.5 clarify → A.6 checklist → B slice → C.5 analyze? → C
│
create-spine-tasks skill → PROMPT.md + STATUS.md (+ dependencies.json edits)
→ optional _explore/ and _authoring/ artifacts
spine-orchestrator extension → Slash commands, batch guidance
spine CLI → tasks validate, tasks analyze, plan, batch start, gates
├─ .spine/agents/worker.md → Worker standing orders (checkpoint discipline)
├─ .spine/agents/reviewer.md → Reviewer rubric
└─ .spine/spine-config.json → tasks root, testing commands, lanes, gates
The skill only creates and updates task files. Execution behavior lives in pi-spine and the worker/reviewer agent prompts. Authoring artifacts under {tasksRoot}/_explore/ and {tasksRoot}/_authoring/ inform decomposition — they are not batch engine input.
Prerequisites
If .spine/spine-config.json does not exist, the project has not been initialized. Tell the user to run spine init first — the skill needs paths.tasksRoot (default spine-tasks/) and testing commands.
Migrants from Taskplane: spine migrate-from-taskplane or spine init --tasks-root taskplane-tasks keeps existing TP-* folders. Use the configured tasks root and ID prefix from {tasksRoot}/CONTEXT.md, not hard-coded spine-tasks/.
What ships with it
6 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.
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 · 612 lines · 82 tokens per session scan A fe8f69a6c879
create-spine-tasks is a skill published in the GitHub repository beettlle/pi-spine (3 stars, last pushed 4d ago), licensed MIT. It adds 82 tokens to every session and 9,765 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…