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/srbryers/slope/slope-review-loopgit clone --depth 1 https://github.com/srbryers/slopeWrote 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/srbryers/slope/slope-review-loop)<a href="https://agentmods.dev/rules/srbryers/slope/slope-review-loop"><img src="https://agentmods.dev/badge/rules/srbryers/slope/slope-review-loop.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.00009 | $0.00234 |
| Opus 5 | $0.00005 | $0.00117 |
| Sonnet 5 | $0.00002 | $0.00047 |
| Haiku 4.5 | $0.00001 | $0.00023 |
Grade A, and why
slope-review-loop 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 3d 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
Sprint Plan Review Loop
After creating a sprint plan, run a structured review.
Review Tier Selection
| Tier | Rounds | When to use |
|---|---|---|
| Skip | 0 | Research, infra, or docs-only sprints |
| Light | 1 | 1-2 tickets, familiar patterns, single-package |
| Standard | 2 | 3-4 tickets, multi-package, or schema/API changes |
| Deep | 3 | 5+ tickets, new infrastructure, architectural changes |
Round 1 — Deep Review
- Does the plan duplicate existing infrastructure?
- Are dependencies correct and ordering optimal?
- Does the approach match codebase patterns?
- Are there scope gaps or underscoped complexity?
Round 2 — Delta Review (Standard+)
Review only what changed since Round 1.
Round 3 — Final Sign-off (Deep only)
Delta review of Round 2 changes. Expected outcome: approval with minor notes.
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.
- 3d ago First seen · 34 lines · 9 tokens per session scan A 0850d14e807d
slope-review-loop is a cursor rule published in the GitHub repository srbryers/slope (6 stars, last pushed 3d ago), licensed MIT. It adds 9 tokens to every session and 234 once invoked, about $0.0000 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-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.
family-instance-domain-actions
Family instance domain action implementation patterns.