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/nitingupta220/riperflow/cursorgit clone --depth 1 https://github.com/nitingupta220/riperflowWhat 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.00313 | $0.00313 |
| Opus 5 | $0.00156 | $0.00156 |
| Sonnet 5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00031 | $0.00031 |
Grade A, and why
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 2d 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
Riperflow Σ
2026 | v1.0
Ω₁=🔍R→ℙ(Ω₁)→Research
Ω₂=💡I→ℙ(Ω₂)→Innovate Ω₃=📝P→ℙ(Ω₃)→Plan Ω₄=⚙️E→ℙ(Ω₄)→Execute Ω₅=🔎RV→ℙ(Ω₅)→Review
📂memory-bank/ Σ₁📋projectbrief.md Σ₂🏛️systemPatterns.md Σ₃💻techContext.md Σ₄🔮activeContext.md Σ₅📊progress.md Σ₆🛡️protection.md
ℙ(Ω₁)={R:✓,C:✗,U:✗,D:✗}
ℙ(Ω₂)={R:✓,C:,U:✗,D:✗}
ℙ(Ω₃)={R:✓,C:✓,U:,D:✗}
ℙ(Ω₄)={R:✓,C:✓,U:✓,D:~}
ℙ(Ω₅)={R:✓,C:✗,U:✗,D:✗}
/r/research /i/innovate /p/plan /e/execute /rev/review
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.
- 2d ago First seen · 25 lines · 313 tokens per session scan A 8860cf60a01a
cursor is a cursor rule published in the GitHub repository nitingupta220/riperflow (19 stars, last pushed 1mo ago), licensed MIT. It adds 313 tokens to every session, about $0.0016 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-30.
Other cursor rules, from other repositories
language-agnostic-patterns
Language-agnostic programming patterns: SOLID, design patterns, clean code, and architecture. Load when refactoring, designing abstractions, or reviewing structure — not for everyday syntax.
cursor-tools-mastery
Cursor 3.7 runtime guide: choose the right tool, canvases, Design Mode, /worktree, /best-of-n, Await, and parallel execution where safe.
cursor-agent-orchestration
Cursor 3.7 orchestration guide: when to plan, when to delegate, nested subagents, multi-environment handoffs, /best-of-n, and Await for long-running branches.
fable5-reasoning
Fable 5 reasoning protocols: task interpretation, risk-first decomposition, approach selection, interleaved thinking, hypothesis ledgers, premortems, calibration, and the stuck-strategy ladder. Load for complex, ambiguous, or long-horizon tasks, for debugging strategy, or whenever progress stalls.
cursor-mcp-optimization
Cursor 3.7 MCP optimization: browser Design Mode, canvases, Figma, Cloudflare tools, MCP Apps structured content, and direct action patterns.
minimax-m3-self-evolution
MiniMax M3 self-evolution harness: iterative refinement loops, compress-before-iterate, autonomous debugging, and recursive improvement patterns.