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-code-style-and-readabilitygit 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-code-style-and-readability)<a href="https://agentmods.dev/rules/toptalentcoder/cursor-awesomerules/general-code-style-and-readability"><img src="https://agentmods.dev/badge/rules/toptalentcoder/cursor-awesomerules/general-code-style-and-readability.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.00152 | $0.00152 |
| Opus 5 | $0.00076 | $0.00076 |
| Sonnet 5 | $0.00030 | $0.00030 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
general-code-style-and-readability 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-code-style-and-readability — 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
- Write code that is readable, understandable, and maintainable for future readers.
- Aim to create software that is not only functional but also readable, maintainable, and efficient throughout its lifecycle.
- Prioritize clarity to make reading, understanding, and modifying code easier.
- Adhere to established coding standards and write well-structured code to reduce errors.
- Regularly review and refactor code to improve structure, readability, and maintainability. Always leave the codebase cleaner than you found it.
- Use version control systems (e.g., Git) to track changes and collaborate effectively.
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 · 10 lines · 152 tokens per session scan A 6efdac0f41d3
general-code-style-and-readability is a cursor rule published in the GitHub repository toptalentcoder/Cursor-AwesomeRules (6 stars, last pushed 1y ago), licensed CC0-1.0. It adds 152 tokens to every session, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to general-code-style-and-readability, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
code-review
Prior to submitting or pushing code to Github, these steps should be reviewed.
commit.detail
Commit 全文規約（gate 清單、Single Session Lock、WIP 處置決策樹、main worktree 預設位置、ad-hoc git commit --only 紀律與 Verify / Recovery、路徑白名單、trunk hard gate、Stash 自動處置 gate、分組與訊息規範、Tag 位置 release hard gate）；always-load 的薄 pointer 在 [[commit]]，觸發時機是「下任何 git commit / git add / git stash / git tag / git push --tags / git push origin v /…
contributing
Cursor rule "contributing" from groupultra/telegram-search, covering contribution & refactor guidelines, 1. before large changes (refactors, new infra, new domains), 2. backend mindset, 3. typescript style and 4. pr hygiene.
workflow
Git branching strategy, commit conventions, and pull request workflow.
safeword-pr-readiness
Prepare a pull request for human review and decide whether it may leave Draft. Use when creating or rewriting a PR description, marking a PR ready, responding to review, or checking mergeability.
pr-standards
Git Commit & PR Standards for AI-Assisted Development.