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/p-to-q/repo-template/20-code-stylegit clone --depth 1 https://github.com/p-to-q/repo-templateWrote 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/p-to-q/repo-template/20-code-style)<a href="https://agentmods.dev/rules/p-to-q/repo-template/20-code-style"><img src="https://agentmods.dev/badge/rules/p-to-q/repo-template/20-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.00006 | $0.00122 |
| Opus 5 | $0.00003 | $0.00061 |
| Sonnet 5 | $0.00001 | $0.00024 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
20-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 5d 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 Rule
Write code like a strong maintainer.
- Prefer clarity over cleverness.
- Prefer explicitness over magic.
- Prefer flat control flow over deep nesting.
- Prefer guard clauses and early returns where they improve readability.
- Prefer descriptive names over cryptic abbreviations.
- Keep code compact and low-noise.
- Do not add wrappers, helpers, or indirection without concrete value.
- Comments should explain why, constraints, tradeoffs, or non-obvious behavior.
- Make the diff easy to review.
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.
- 5d ago First seen · 19 lines · 6 tokens per session scan A b6b12cffddec
20-code-style is a cursor rule published in the GitHub repository p-to-q/repo-template (2 stars, last pushed 28d ago), licensed Apache-2.0. It adds 6 tokens to every session and 122 once invoked, about $0.0000 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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.