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/stet-integrationgit 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/stet-integration)<a href="https://agentmods.dev/rules/beettlle/pi-spine/stet-integration"><img src="https://agentmods.dev/badge/rules/beettlle/pi-spine/stet-integration.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 | $0.00015 | $0.00494 |
| Opus 5 | $0.00008 | $0.00247 |
| Sonnet 5 | $0.00003 | $0.00099 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
stet-integration 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 5d 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
Stet integration
When the user asks to dismiss findings, run stet, or triage reviews, use the commands and dismiss reasons below.
Commands
| Command | Description |
|---|---|
stet doctor |
Verify Ollama, Git, models |
stet start [ref] |
Start review from baseline |
stet run |
Re-run incremental review |
stet finish |
Persist state, clean up |
stet list |
List active findings with IDs |
stet status |
Show session status |
stet dismiss <id> [reason] |
Mark finding dismissed; prefer giving a reason (feeds optimize/shadowing). Also: stet rerun, stet cleanup, stet optimize. |
Dismiss reasons
Valid values for stet dismiss <id> <reason>: false_positive, already_correct, wrong_suggestion, out_of_scope.
| Reason | Use when |
|---|---|
| false_positive | Not a real issue; model misread; redundant or low-signal nit. |
| already_correct | Code already correct; concern addressed; finding about removed lines fixed by the change. |
| wrong_suggestion | Suggestion wrong or harmful (wrong tool, would make code inconsistent). |
| out_of_scope | Wrong scope (e.g. generated files, meta/curated docs). |
Quick pick: Worse/inconsistent → wrong_suggestion; wrong scope → out_of_scope; already correct → already_correct; else → false_positive.
❌ Bad: stet dismiss abc123 with no reason when user said "not useful"; or using a reason that doesn't match (e.g. wrong_suggestion when it's noise).
✅ Good: stet dismiss abc123 false_positive (or the reason that matches); prefer giving a reason.
📍 See: Project docs/review-quality.md (or stet README) for examples.
Review model (when stet injects this rule)
Report only actionable findings; prefer fewer, high-confidence. Do not report issues that exist only in removed lines (-) and are already fixed by the added lines (+).
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.
- 5d ago First seen · 42 lines · 15 tokens per session scan A 0bad21e720c9
stet-integration is a cursor rule published in the GitHub repository beettlle/pi-spine (3 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 494 once invoked, about $0.0001 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
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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.