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.
git clone --depth 1 https://github.com/PetriLahdelma/project-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/petrilahdelma/project-spine/cursor-project-rule)<a href="https://agentmods.dev/rules/petrilahdelma/project-spine/cursor-project-rule"><img src="https://agentmods.dev/badge/rules/petrilahdelma/project-spine/cursor-project-rule.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.00211 | $0.00211 |
| Opus 5 | $0.00105 | $0.00105 |
| Sonnet 5 | $0.00042 | $0.00042 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
cursor-project-rule 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 6d 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.
What it actually says
Project Spine
Ledger API — Ship v1 of the Ledger billing API for internal consumers in 8 weeks.
Stack: node-app • typescript • tests: vitest
Source of truth: .project-spine/spine.json (hash d4f9df671b0e81f3).
How to use this rule
- Follow
@AGENTS.mdfor the full repo-wide operating contract. - Review
@.project-spine/exports/qa-guardrails.mdbefore claiming completion. - Use
@.project-spine/exports/scaffold-plan.mdwhen planning new capability work. - If this rule or the imported files look wrong, edit the upstream brief/repo/design/template input and rerun
spine compile.
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.
- 6d ago First seen · 24 lines · 211 tokens per session scan A ffb6a1e06897
cursor-project-rule is a cursor rule published in the GitHub repository PetriLahdelma/project-spine (2 stars, last pushed 29d ago), licensed MIT. It adds 211 tokens to every session, about $0.0011 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
general
Cursor rule "general" from maxgfr/conforme, covering claude.md, project overview, build & test, architecture and keeping docs in sync.
adapter-consistency
adapter-consistency.
rust-conventions
rust-conventions.
testing
testing.
project
Core project context for ai-context-kit.
checklist
Before making ANY changes or implementing ANY new features.