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/nedcodes-ok/cursorrules-collectionWrote 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/nedcodes-ok/cursorrules-collection/csharp)<a href="https://agentmods.dev/rules/nedcodes-ok/cursorrules-collection/csharp"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/csharp/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/nedcodes-ok/cursorrules-collection/csharp"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/csharp.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.00282 | $0.00282 |
| Opus 5.5 | $0.00113 | $0.00113 |
| Sonnet 5.5 | $0.00056 | $0.00056 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
csharp 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.
What it actually says
C# Cursor Rules
You are an expert C# developer. Follow these rules:
Code Style
- Target C# 12+ / .NET 8+. Use file-scoped namespaces, primary constructors
- Use records for immutable data types, classes for entities with behavior
- Use pattern matching (switch expressions, is patterns)
- Follow Microsoft naming: PascalCase public, _camelCase private fields
Design
- Use dependency injection everywhere
- Prefer interfaces for contracts, abstract classes only for shared implementation
- Use Options pattern for configuration binding
- Seal classes by default
Async
- Use async/await for all I/O. Suffix async methods with "Async"
- Use ValueTask for hot paths completing synchronously
- Never use .Result or .Wait() — deadlock risk
- Use CancellationToken for all async operations
Null Safety
- Enable nullable reference types project-wide
- Use ?. and ?? operators
- Validate with ArgumentNullException.ThrowIfNull()
- Return empty collections instead of null
Testing
- Use xUnit, FluentAssertions, NSubstitute
- Name: MethodName_Scenario_ExpectedResult
- Use Theory + InlineData for parameterized tests
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 · 39 lines · 282 tokens per session scan A 8eeffd11d04d
csharp is a cursor rule published in the GitHub repository nedcodes-ok/cursorrules-collection (38 stars, last pushed 7mo ago), licensed MIT. It adds 282 tokens to every session, about $0.0011 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
dotnet-build
Rules and best practices for .NET build systems.
coding-style
his file provides guidelines for writing clean, maintainable, and idiomatic C# code with a focus on functional patterns and proper abstraction.
benchmarking
Designing benchmarks for measuring .NET performance.
dependency-management
This file provides guidelines for safely managing NuGet package dependencies in .NET projects, focusing on security, licensing, and maintainability.
solution-management
This file provides guidelines for maintaining .NET solutions with consistent SDK versions, shared metadata, and centralized package management.
consuming-dotnettool
This tool is used for helping manage and organize the installation of dotnet tool instances that are used for .NET projects.