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/mhmdreza-rafiei/agent-tools/code-stylegit clone --depth 1 https://github.com/mhmdreza-rafiei/agent-toolsWrote 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/mhmdreza-rafiei/agent-tools/code-style)<a href="https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/code-style"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/code-style.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 | $0.00024 | $0.00396 |
| Opus 5 | $0.00012 | $0.00198 |
| Sonnet 5 | $0.00005 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
code-style 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 3d 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
Code style
Applies when writing or refactoring code. Not every chat — load when the
task touches code. Pairs with files-folders-structure (which owns paths;
this owns in-code style).
Formatting
- Follow the project's existing formatter config (prettier, black, gofmt, rustfmt). If none exists, do not invent one — ask.
- One statement per line; no chained ternaries; no
&&/||for control flow where anifis clearer. - Trailing commas where the language allows (diff-friendly).
Naming
- Match the surrounding code's convention (camelCase / snake_case). Do not mix conventions within a file.
- Names describe what, not how:
pendingOrders, notarray1. - Booleans read as yes/no:
isActive,hasAccess,canWrite. - Avoid abbreviations except domain-standard ones (
url,id,db).
Structure
- One responsibility per function; if a function needs a comment to explain what it does, split it.
- Pure where cheap; side effects at the edges (handlers, controllers).
- Early returns for the unhappy path; the happy path stays unindented.
When in doubt
- Read three neighbors; mimic the majority.
- If the project has a linter, its output is the spec — do not argue with it.
Do not
- Reformat code outside the change you own (noise diffs).
- Introduce a new pattern where an existing one fits.
- Rename user-stated field names (
phonestaysphone).
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.
- 3d ago First seen · 46 lines · 24 tokens per session scan A 60171d5e27da
code-style is a cursor rule published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 16d ago), licensed MIT. It adds 24 tokens to every session and 396 once invoked, about $0.0001 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
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.
family-instance-domain-actions
Family instance domain action implementation patterns.