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/johnpeterman72/CursorRIPER.agentWrote 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/johnpeterman72/cursorriper.agent/riper-sigma-core)<a href="https://agentmods.dev/rules/johnpeterman72/cursorriper.agent/riper-sigma-core"><img src="https://agentmods.dev/badge/rules/johnpeterman72/cursorriper.agent/riper-sigma-core/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/rules/johnpeterman72/cursorriper.agent/riper-sigma-core"><img src="https://agentmods.dev/badge/rules/johnpeterman72/cursorriper.agent/riper-sigma-core.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.00380 | $0.00380 |
| Opus 5.5 | $0.00152 | $0.00152 |
| Sonnet 5.5 | $0.00076 | $0.00076 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
riper-sigma-core 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 1mo 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
RIPER·Σ Core Protocol v1.0.3
Modes & Permissions
Ω₁·R: READ-ONLY (Γ₁₋₃,₆) Ω₂·I: IDEATE (no code) Ω₃·P: SPECIFY (exact plans) Ω₄·E: EXECUTE (plan only) Ω₅·V: VALIDATE (no fix)
State Machine
σ₄.Ω_current ∈ [Ω₁..Ω₅] FLOW: Ω₁→Ω₂→Ω₃→Ω₄→Ω₅ ENFORCE: current==agent_mode
Memory Protocol
σ₁: brief | σ₂: patterns | σ₃: tech σ₄: context+STATE | σ₅: progress | σ₆: protection
Handoff Protocol
EXIT: /handoff→σ₄{to:Ω_next,summary} ENTRY: CHECK(σ₄.Ω_current==my_mode)
Protection Levels
Ψ₁-₃: proceed | Ψ₄-₆: caution+confirm
Commands
/r=Ω₁ /i=Ω₂ /p=Ω₃ /e=Ω₄ /rev=Ω₅
Cross-Reference Notation
[↗️σₓ:Rₓ] = Reference to memory file section Γ₁=Files Γ₂=Folders Γ₃=Code Γ₄=Commands Γ₅=Modify Γ₆=Web
Session Protocol
SESSION: @σ₄.Ω_session (maintained across modes) LOCK: σ₄.locked_by (prevent concurrent updates)
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.
- 1mo ago First seen · 40 lines · 380 tokens per session scan A f2dd65f15c99
riper-sigma-core is a cursor rule published in the GitHub repository johnpeterman72/CursorRIPER.agent (15 stars, last pushed 1y ago), licensed MIT. It adds 380 tokens to every session, about $0.0015 per session on Opus 5.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-30.
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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).