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/toptalentcoder/cursor-awesomerules/general-project-practicesgit clone --depth 1 https://github.com/toptalentcoder/Cursor-AwesomeRulesWrote 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/toptalentcoder/cursor-awesomerules/general-project-practices)<a href="https://agentmods.dev/rules/toptalentcoder/cursor-awesomerules/general-project-practices"><img src="https://agentmods.dev/badge/rules/toptalentcoder/cursor-awesomerules/general-project-practices.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.00140 | $0.00140 |
| Opus 5 | $0.00070 | $0.00070 |
| Sonnet 5 | $0.00028 | $0.00028 |
| Haiku 4.5 | $0.00014 | $0.00014 |
Grade A, and why
general-project-practices 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.
This is a copy
100% identical to general-project-practices — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
- Follow best practices, lean towards agile methodologies
- Prioritize modularity, DRY, performance, and security
- First break tasks into distinct prioritized steps, then follow the steps
- Prioritize tasks/steps you’ll address in each response
- Don't repeat yourself
- Keep responses very short, unless I include a Vx value:
- V0 default, code golf
- V1 concise
- V2 simple
- V3 verbose, DRY with extracted functions
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 · 14 lines · 140 tokens per session scan A 1299a5c59086
general-project-practices is a cursor rule published in the GitHub repository toptalentcoder/Cursor-AwesomeRules (6 stars, last pushed 1y ago), licensed CC0-1.0. It adds 140 tokens to every session, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to general-project-practices, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
reflection-basic
Basic reflection format for Level 2 Simple Enhancement tasks.
cursor-fable-rules
Fable coding lifecycle discipline and situational awareness for Cursor.
git-workflow
Rules for git operations, commit strategy, and GitHub CLI usage.
feedback-enhanced
Enhanced feedback mechanism with 1-hour timeout - 增强反馈机制，1小时超时.
122-swift-development
122: Swift development workflow including TDD, refactoring, and performance optimization.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.