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-commit-disciplinegit 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.00255 | $0.00255 |
| Opus 5 | $0.00128 | $0.00128 |
| Sonnet 5 | $0.00051 | $0.00051 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
slope-commit-discipline 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
Commit Discipline
Commit early, commit often. The last push is the recovery point.
Commit triggers:
Commit immediately after ANY of these:
- Each new file — route, migration, config, component, test
- Each endpoint or feature implemented
- Each migration — commit separately
- Each bug fix — no matter how small
- Before switching context to a different area
- Before risky operations — large refactor, dependency upgrade
- Time check — if ~15 minutes since last commit, commit what works
- Session end — never leave uncommitted changes (use
wip:prefix if incomplete)
Push triggers:
Push immediately after ANY of these:
- After each completed ticket (Post-Shot Routine)
- Every 30 minutes
- Before switching tickets
- Session end — never leave unpushed commits
Commit message format:
<type>(<ticket>): <short summary in imperative mood>
Types: feat, fix, refactor, docs, test, chore, wip
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 · 38 lines · 255 tokens per session scan A d6672281deff
slope-commit-discipline is a cursor rule published in the GitHub repository srbryers/slope (6 stars, last pushed 2d ago), licensed MIT. It adds 255 tokens to every session, about $0.0013 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
git
Conventional commit message format for git commits.
commit-checks
Run gofmt, go vet, and unit tests before committing Go files.
no-ai-attribution
Never attribute commits, comments, or contributions to AI agents.
git-commit-attribution
Git commits must use the human developer identity only; never Cursor Agent co-authorship.
git-conventional-commits
Conventional commit messages and logical multi-commit workflow when working with Git.
dos-verify-done-claims-cursorrules-prompt-file
Gate AI done/shipped/fixed claims on ground truth from the DOS kernel (dos verify, dos commit-audit) — git ancestry and the commit's own diff, never the agent's own narration.