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/GoranErhartic/cursor-development-rulesWrote 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/goranerhartic/cursor-development-rules/dependencies)<a href="https://agentmods.dev/rules/goranerhartic/cursor-development-rules/dependencies"><img src="https://agentmods.dev/badge/rules/goranerhartic/cursor-development-rules/dependencies/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/goranerhartic/cursor-development-rules/dependencies"><img src="https://agentmods.dev/badge/rules/goranerhartic/cursor-development-rules/dependencies.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.00014 | $0.00785 |
| Opus 5.5 | $0.00006 | $0.00314 |
| Sonnet 5.5 | $0.00003 | $0.00157 |
| Haiku 4.5 | $0.00001 | $0.00078 |
Grade A, and why
dependencies 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 1mo 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependencies & NuGet
Central Package Management
Use Directory.Packages.props in solution root:
<Project>
<PropertyGroup>
<ManagePackageVersionsCentrally>true</ManagePackageVersionsCentrally>
</PropertyGroup>
<ItemGroup>
<!-- Core -->
<PackageVersion Include="FluentValidation" Version="11.*" />
<PackageVersion Include="FluentValidation.DependencyInjectionExtensions" Version="11.*" />
<PackageVersion Include="Serilog.AspNetCore" Version="8.*" />
<PackageVersion Include="Polly" Version="8.*" />
<!-- Data -->
<PackageVersion Include="Microsoft.EntityFrameworkCore.SqlServer" Version="10.*" />
<PackageVersion Include="Microsoft.EntityFrameworkCore.Tools" Version="10.*" />
<!-- Messaging -->
<PackageVersion Include="Rebus" Version="8.*" />
<PackageVersion Include="Rebus.ServiceProvider" Version="5.*" />
<PackageVersion Include="Rebus.RabbitMq" Version="0.*" />
<PackageVersion Include="Rebus.Serilog" Version="6.*" />
<!-- Testing -->
<PackageVersion Include="xunit" Version="2.*" />
<PackageVersion Include="FluentAssertions" Version="6.*" />
<PackageVersion Include="Moq" Version="4.*" />
<PackageVersion Include="Testcontainers.MsSql" Version="3.*" />
<PackageVersion Include="Microsoft.AspNetCore.Mvc.Testing" Version="10.*" />
</ItemGroup>
</Project>
In .csproj files, omit version:
<PackageReference Include="FluentValidation" />
Package Selection Criteria
- ONLY use free and open-source packages
- Acceptable licenses: MIT, Apache 2.0, BSD, LGPL, MPL, or any OSI-approved free license
- STOP and ask before introducing packages with commercial/paid tiers
- Be cautious with copyleft licenses (GPL, AGPL) — they have viral implications
- Verify license before adding any new dependency
- NEVER use packages that require paid licenses for production use
- Favor actively maintained packages with community support
- Verify security — check for known vulnerabilities
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.
- 1mo ago First seen · 107 lines · 14 tokens per session scan A e1980999efc4
dependencies is a cursor rule published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 7mo ago), licensed MIT. It adds 14 tokens to every session and 785 once invoked, about $0.0001 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.