secure-dev-c-sharp

A set of rules for safer C# and .NET code, including input checks, file validation, database queries, and output handling. C# is a programming language, while .NET is the platform and libraries commonly used to run it.

In plain words
What is it for?
Use it when building or reviewing C#/.NET applications that process user input, uploads, database data, or serialized objects.
Why use it?
It reduces security mistakes such as accepting harmful files, unsafe database queries, and dangerous data processing. The rules also show safer patterns for common .NET operations.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/matank001/cursor-security-rules/secure-dev-c-sharp
Clone the repo
git clone --depth 1 https://github.com/matank001/cursor-security-rules
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 948 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00948
Opus 5 $0.00000 $0.00474
Sonnet 5 $0.00000 $0.00190
Haiku 4.5 $0.00000 $0.00095

Measured yesterday against content hash a9ae88a9ffa9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

secure-dev-c-sharp 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 yesterday.

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.

secure-dev-c-sharp.mdc · 107 lines

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.

Secure C#/.NET Development

These rules apply to all C#/.NET code in the repository and aim to prevent common security risks through disciplined use of input validation and deserialization, output encoding, and safe APIs.

All violations must include a clear explanation of which rule was triggered and why, to help developers understand and fix the issue effectively.
Generated code must not violate these rules. If a rule is violated, a comment must be added explaining the issue and suggesting a correction.

1. Validate All external inputs

  • Rule: Validate all external inputs by manually checking the type, format and size of the input manually or by using libraries like FluentValidation. For file validation, utilize MIME Type Validation libraries, like MimeDetective or HeyRed.Mime to check whether a file's type and content actually matches the expected type.

2. Use Parameterized Queries in EntityFramework

  • Rule: Parameterize queries in EntityFramework using LINQ and FromSqlInterpolated.
  • Unsafe:
    // Vulnerable to SQL Injection
    var user = dbContext.Users
      .FromSqlRaw($"SELECT * FROM Users WHERE Username = '{userInput}'")
      .FirstOrDefault();
    
  • Safe:
    //Input is interpolated and parameterized internally
    var user = dbContext.Users
      .FromSqlInterpolated($"SELECT * FROM Users WHERE Username = {userInput}")
      .FirstOrDefault();
    
  • Safe:
    //LINQ is translated into parameterized SQL query
    var user = dbContext.Users
        .Where(u => u.Username == userInput)
        .FirstOrDefault();
    

3. Avoid Singleton Dependency Injection On User-Specific Services

  • Rule: When registering services in ASP.NET Dependency Injection, choose the correct service lifetime to avoid exposing unauthorized users to other users' requests.

  • Unsafe:

    var builder = WebApplication.CreateBuilder(args);
    // One instance is shared for all users - sensitive data is exposed to others
    builder.Services.AddSingleton<UserAuthService>();
    
  • Safe:

    var builder = WebApplication.CreateBuilder(args);
    // Each created instance is scoped for a single request
    builder.Services.AddScoped<UserAuthService>();
    

Read the full file on GitHub · 107 lines

Changes

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.

  1. yesterday First seen · 107 lines · 948 tokens per session scan A a9ae88a9ffa9

Subscribe to this mod's changes

secure-dev-c-sharp is a cursor rule published in the GitHub repository matank001/cursor-security-rules (379 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 948 tokens. 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.