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 rules/beettlle/pi-spine/spine-operator-cursorgit 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/rules/beettlle/pi-spine/spine-operator-cursor)<a href="https://agentmods.dev/rules/beettlle/pi-spine/spine-operator-cursor"><img src="https://agentmods.dev/badge/rules/beettlle/pi-spine/spine-operator-cursor.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.1 | $0.00073 | $0.02539 |
| Opus 5 | $0.00036 | $0.01269 |
| Sonnet 5 | $0.00015 | $0.00508 |
| Haiku 4.5 | $0.00007 | $0.00254 |
Grade A, and why
spine-operator-cursor 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 today.
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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pi-spine operator (Cursor)
Operate pi-spine batches from Cursor: validate, plan, start, monitor, recover, gate, and integrate. Cursor is the operator console—batch workers are pi sessions in lane worktrees, not Cursor Agent.
Related: @spine-task-authoring.mdc for packets; @spine-worker-cursor.mdc for manual implementation when no batch runs. Verification: general-llm-anti-patterns.mdc §3.8–3.9. Normative spec: pi-spine PRD.
Manual activation: @spine-operator-cursor when the agent does not auto-select this rule.
When this rule applies
Apply when the user:
- Runs or asks about
spineCLI (batch, gate, integrate, doctor, dashboard) - Needs batch diagnosis, recovery, or orphan handling
- Wants to land work on
mainvia gate + integrate
Do not apply when authoring packets or implementing task code in the same folders an active batch owns.
Prerequisites
- Node.js ≥ 22, git,
pion PATH .spine/spine-config.json(spine init)- Install:
pi install npm:pi-spineornpm install -g pi-spine
Command reference
| Phase | Commands |
|---|---|
| Setup | spine init, spine doctor, spine migrate-from-taskplane |
| Validate | spine preflight, spine tasks validate, spine tasks analyze |
| Plan | spine plan all, spine plan pending, spine deps |
| Batch | spine batch start <scope>, pause, resume, abort, retry <id>, skip <id> |
| Review | spine review step, spine gate status, spine gate approve, spine gate reject |
| Land | spine integrate, then post-integrate npm run release:check on main |
| Observe | spine status, spine status --diagnose, spine journal, spine dashboard, spine next |
Attached vs detached: Prefer spine batch start <scope> --attached until the operator trusts detached recovery. After detached start, always run spine status --diagnose.
Stub workers (CI / no pi): SPINE_WORKER_STUB=1 spine batch start <id>.
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.
- today Changed · +13 lines da891f47c679
- 5d ago First seen · 173 lines · 73 tokens per session scan A 9e80a4ac6015
spine-operator-cursor is a cursor rule published in the GitHub repository beettlle/pi-spine (3 stars, last pushed yesterday), licensed MIT. It adds 73 tokens to every session and 2,539 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.