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/cursorrulesgit clone --depth 1 https://github.com/srbryers/slopeWhat 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.00299 | $0.00299 |
| Opus 5 | $0.00150 | $0.00150 |
| Sonnet 5 | $0.00060 | $0.00060 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
cursorrules 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 yesterday.
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
SLOPE Project
This project uses the SLOPE framework for sprint tracking.
Commands
slope card— view handicap cardslope validate— validate scorecardsslope review— generate sprint reviewslope briefing— pre-round briefing
MCP Tools
A SLOPE MCP server is configured in .cursor/mcp.json. Two tools:
search— discover API functions, types, constantsexecute— run JS with full SLOPE API in sandbox
Sprint Workflow
- Pre-Hole:
slope briefingfor handicap, hazards, gotchas - Per-Shot: classify each ticket with approach + result + hazards
- Post-Hole:
slope validatescorecard,slope review, update common-issues
Approach Complexity
- Driver: risky/new territory
- Long Iron: multi-package changes
- Short Iron: standard work
- Wedge: small tasks
- Putter: trivial changes
Shot Results
- In the Hole: perfect execution
- Green: landed correctly
- Fairway: clean start, needs finishing
- Miss directions: over-scoped, under-scoped, wrong approach, drift
Scorecards
Stored in docs/retros/sprint-N.json. See .slope/config.json for configuration. See .cursor/rules/ for detailed checklists.
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.
- yesterday First seen · 37 lines · 299 tokens per session scan A 38395cfc0bc6
cursorrules is a cursor rule published in the GitHub repository srbryers/slope (6 stars, last pushed yesterday), licensed MIT. It adds 299 tokens to every session, about $0.0015 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
test-plan
Plan Katalon True Platform/TestOps testing for a release, sprint, or feature. Use when you need to translate quality goals into scope, prioritize testing by requirement coverage and risk, decide what to test first, or build the executable plan structure (folders, suites, and sprint/release association) that stands in…
cli-forge-schema
Generate GitHub-compatible Mermaid diagrams — auto-picks diagram type, splits complex ones, converts tables/kanban/PERT.
STAGE_S5_TEST_POINTS
AIDocxWorkFlow Stage 5 — 测试点生成（独立阶段）.
sprint-planning
BMAD BMM Agent: sprint-planning.
head-of-product
Head of Product persona — planning, user stories, UX decisions, scope guardian. Use when discussing product strategy, PRDs, user research, feature proposals, or backlog prioritization.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.