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/linuxchata/ai-playbookWrote 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/linuxchata/ai-playbook/csharp-coding-standards)<a href="https://agentmods.dev/rules/linuxchata/ai-playbook/csharp-coding-standards"><img src="https://agentmods.dev/badge/rules/linuxchata/ai-playbook/csharp-coding-standards/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/linuxchata/ai-playbook/csharp-coding-standards"><img src="https://agentmods.dev/badge/rules/linuxchata/ai-playbook/csharp-coding-standards.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.00053 | $0.03619 |
| Opus 5.5 | $0.00021 | $0.01448 |
| Sonnet 5.5 | $0.00011 | $0.00724 |
| Haiku 4.5 | $0.00005 | $0.00362 |
Grade A, and why
csharp-coding-standards 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 — 565 lines — stays where its author put it; the contents beside it link to each section on GitHub.
C# Coding Standards
Description
Defines the C# coding standards, patterns, and conventions to be applied consistently across all C# projects. Rules cover naming, structure, async patterns, null handling, dependency injection, logging, result patterns, and formatting. Apply these rules uniformly in all production code.
1. File & Namespace Structure
1.1 File-Scoped Namespaces
Always use file-scoped namespaces:
// ✅ Correct
namespace MyApp.Core.Validators;
internal class OrderValidator { }
// ❌ Wrong
namespace MyApp.Core.Validators
{
internal class OrderValidator { }
}
1.2 Using Directives
- Place
usingdirectives outside the namespace. - Group: System namespaces first, then others ordered alphabetically – separated by a blank line.
- Use implicit usings where available; add explicit usings only when needed for disambiguation.
using System.Text;
using System.Text.Json;
using Microsoft.Extensions.Logging;
using MyApp.Core.Abstractions;
using MyApp.Domain;
1.3 One Type Per File
Each file contains exactly one top-level type. The file name must match the type name exactly.
2. Naming Conventions
2.1 Types
| Kind | Convention | Example |
|---|---|---|
| Classes | PascalCase | OrderValidator, UserService |
| Interfaces | I prefix + PascalCase |
IOrderRepository, IUserService |
| Enums | PascalCase | OrderStatus, PaymentMethod |
| Structs | PascalCase | Money, DateRange |
| Records | PascalCase | AppConfiguration, UserSettings |
2.2 Members
| Kind | Convention | Example |
|---|---|---|
| Public properties | PascalCase | CreatedAt, TotalAmount |
| Public methods | PascalCase | CreateOrder, ValidatePayment |
| Private fields | _camelCase (underscore prefix) |
_repository, _logger |
| Constants | PascalCase | DefaultTimeout, MaxRetryCount |
| Local variables | camelCase | orderId, serializedData |
| Method parameters | camelCase | cancellationToken, userId |
| Lambda parameters | Short camelCase | x =>, e =>, o => |
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 · 565 lines · 53 tokens per session scan A c73be6669ad7
csharp-coding-standards is a cursor rule published in the GitHub repository linuxchata/ai-playbook (7 stars, last pushed 5mo ago), licensed MIT. It adds 53 tokens to every session and 3,619 once invoked, about $0.0002 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-31.
Other cursor rules, from other repositories
csharp
Rules applied when working in C# / .NET files.
java-kotlin
Rules applied when working in Java or Kotlin files (incl. Android).
php
Rules applied when working in PHP files (incl. Laravel, Symfony, WordPress).
ruby
Rules applied when working in Ruby files (incl. Rails).
python
Rules applied when working in Python files.
java-backend
Java Backend Execution Agent (Spring Boot / Quarkus).