csharp-api-controller-standards

A set of coding rules for ASP.NET Core REST API controllers, which are classes that receive web requests and return responses. It covers routes, HTTP methods, response types, documentation, dependency injection, and asynchronous code.

In plain words
What is it for?
Use it when creating or reviewing C# ASP.NET Core controllers and their web API endpoints.
Why use it?
It keeps an API's endpoints consistent, predictable, and documented across the project.

Cursor rule for Cursor

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/linuxchata/ai-playbook/csharp-api-controller-standards
Clone the repo
git clone --depth 1 https://github.com/linuxchata/ai-playbook

Made for: Cursor.

Per session 55 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,879 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.00055 $0.01879
Opus 5 $0.00028 $0.00940
Sonnet 5 $0.00011 $0.00376
Haiku 4.5 $0.00006 $0.00188

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

Security

Grade A, and why

csharp-api-controller-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 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.

.cursor/rules/csharp-api-controller-standards.mdc · 238 lines

How it starts

The opening of the file, as written. The whole thing — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.

C# ASP.NET Core API Controller Standards

Description

Defines the coding standards, patterns, and conventions for ASP.NET Core REST API controllers. Rules cover routing, HTTP verbs, response types, XML documentation, dependency injection, and asynchronous execution. Apply these rules uniformly to ensure a consistent, predictable, and well-documented API surface.


1. Controller Structure & Inheritance

1.1 Base Class and Attributes

  • All API controllers must inherit from ControllerBase (not Controller, which includes view rendering logic).
  • Decorate all controllers with the [ApiController] attribute to enable automatic model validation, API behavior conventions, and attribute routing requirements.
  • Use the [Route] attribute at the class level to define the base path.
// ✅ Correct
[ApiController]
[Route("api/[controller]")]
public sealed class OrdersController : ControllerBase
{
}

// ❌ Wrong
public class OrdersController : Controller { }

2. Routing Conventions

2.1 Resource Naming

  • Use nouns, not verbs, for endpoint paths.
  • Prefer [controller] in the Route attribute to automatically use the controller name (minus the "Controller" suffix).

2.2 Route Parameters

  • Specify route parameters explicitly in the HTTP verb attributes.
  • Match route parameter names exactly with the method parameter names.
[HttpGet("{id:guid}")]
public async Task<IActionResult> GetByIdAsync(Guid id, CancellationToken cancellationToken)

3. HTTP Methods & Attributes

3.1 Standard Verbs

Use the correct HTTP verb corresponding to the operation:

Verb Usage Idempotent
[HttpGet] Retrieve a resource or collection Yes
[HttpPost] Create a new resource or execute an action No
[HttpPut] Fully update an existing resource Yes
[HttpPatch] Partially update an existing resource No
[HttpDelete] Remove a resource Yes

3.2 Action Parameters Binding

Read the full file on GitHub · 238 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 · 238 lines · 55 tokens per session scan A 7971c8121111

Subscribe to this mod's changes

csharp-api-controller-standards is a cursor rule published in the GitHub repository linuxchata/ai-playbook (6 stars, last pushed 3mo ago), licensed MIT. It adds 55 tokens to every session and 1,879 once invoked, about $0.0003 per session on Opus 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.