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-post-hole-routinegit 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-post-hole-routine)<a href="https://agentmods.dev/rules/srbryers/slope/slope-post-hole-routine"><img src="https://agentmods.dev/badge/rules/srbryers/slope/slope-post-hole-routine.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.1 | $0.00000 | $0.00307 |
| Opus 5 | $0.00000 | $0.00153 |
| Sonnet 5 | $0.00000 | $0.00061 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
slope-post-hole-routine 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
SLOPE Post-Hole Routine (Sprint Completion)
When you have just completed a sprint and filed a scorecard (e.g. docs/retros/sprint-N.json), always run the full Post-Hole routine before considering the sprint done:
-
Validate — Run
slope validate docs/retros/sprint-N.json(or from repo root:node dist/cli/index.js validate docs/retros/sprint-N.jsonif slope is not on PATH). Fix any validation errors. -
Review — Run
slope review docs/retros/sprint-N.jsonand save the output todocs/retros/sprint-N-review.mdso the sprint review markdown is committed with the scorecard. -
Distill learnings — If the sprint revealed a recurring pattern, gotcha, or prevention tactic, add it to
.slope/common-issues.json(recurring_patterns array). If nothing to add, skip. -
Commit — Commit the review file and any common-issues updates together with the scorecard (or in a follow-up commit).
Do not skip validate or review. The routine keeps the handicap and briefing data accurate and leaves a readable review for future sprints.
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 · 20 lines · 0 tokens per session scan A f4f3f2809c17
slope-post-hole-routine is a cursor rule published in the GitHub repository srbryers/slope (6 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 307 tokens. 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
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.
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.