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/paulpham157/paul-s-cursor-rules/development-process-rulesgit clone --depth 1 https://github.com/paulpham157/paul-s-cursor-rulesWhat 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.00000 | $0.00052 |
| Opus 5 | $0.00000 | $0.00026 |
| Sonnet 5 | $0.00000 | $0.00010 |
| Haiku 4.5 | $0.00000 | $0.00005 |
Grade A, and why
development-process-rules 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- development-process-rules — 100% identical, 0 lines differ
- development-process-rules — 100% identical, 0 lines differ
What it actually says
- Make changes in small, incremental steps.
- Test changes thoroughly before committing.
- Document changes clearly in commit messages.
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 · 7 lines · 52 tokens per session scan A c183a8bf73e4
development-process-rules is a cursor rule published in the GitHub repository paulpham157/paul-s-cursor-rules (27 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 52 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-30.
Other cursor rules, from other repositories
engineering-ticket-template-cursorrules-prompt-file
Cursor rules for engineering development with ticket template integration.
ankra-cli
Ankra CLI rules and best practices for managing Kubernetes clusters via the Ankra platform.
cypress-integration-testing-cursorrules-prompt-file
Cursor rules for Cypress development with integration testing.
go-backend-scalability-cursorrules-prompt-file
Cursor rules for Go development with backend scalability.
git-conventional-commit-messages
Cursor rules for Git development with conventional commit messages integration.
cypress-accessibility-testing-cursorrules-prompt-file
Cursor rules for Cypress development with accessibility testing.