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.
git clone --depth 1 https://github.com/jahands/promptsWrote 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/jahands/prompts/cursor-rules)<a href="https://agentmods.dev/rules/jahands/prompts/cursor-rules"><img src="https://agentmods.dev/badge/rules/jahands/prompts/cursor-rules/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/jahands/prompts/cursor-rules"><img src="https://agentmods.dev/badge/rules/jahands/prompts/cursor-rules.svg" alt="Reviewed on agentmods" width="80" 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.00011 | $0.02453 |
| Opus 5.5 | $0.00004 | $0.00981 |
| Sonnet 5.5 | $0.00002 | $0.00491 |
| Haiku 4.5 | $0.00001 | $0.00245 |
Grade A, and why
cursor-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 19d 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.
How it starts
The opening of the file, as written. The whole thing — 453 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remember: Empty sections add tokens but no value. Less structure often communicates more clearly.
That's it. Don't add sections unless they add real value.
<rule-name>
<title>Rule Title</title>
<rules>
- First requirement
- Second requirement
- Third requirement
</rules>
<examples>
<example type="good">
```typescript
// Good code example
For most rules, you're done. Only add more sections if the rule is genuinely complex.
<rule-name>
<title>Rule Title</title>
<context>
<applies-to>Where this rule applies</applies-to>
</context>
<overview>High-level explanation</overview>
<key-concepts>
- Important concept
- Another concept
</key-concepts>
<rules>
<rule>
<name>Rule name</name>
<requirements>
- Requirement
- Another requirement
</requirements>
</rule>
</rules>
<examples>
<example type="good">
```typescript
// Code
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.
- 19d ago Changed · -4 lines · -2 tokens per session 6b4facf8ec13
- 1mo ago First seen · 457 lines · 13 tokens per session scan A 254a9ff9d86d
cursor-rules is a cursor rule published in the GitHub repository jahands/prompts (19 stars, last pushed 12d ago), licensed MIT. It adds 11 tokens to every session and 2,453 once invoked, about $0.0000 per session on Opus 5.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-30.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.