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.
npx skills add linuxchata/ai-playbook --skill csharp-api-controller-standardsgit 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/skills/linuxchata/ai-playbook/csharp-api-controller-standards)<a href="https://agentmods.dev/skills/linuxchata/ai-playbook/csharp-api-controller-standards"><img src="https://agentmods.dev/badge/skills/linuxchata/ai-playbook/csharp-api-controller-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/skills/linuxchata/ai-playbook/csharp-api-controller-standards"><img src="https://agentmods.dev/badge/skills/linuxchata/ai-playbook/csharp-api-controller-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.00063 | $0.01896 |
| Opus 5.5 | $0.00025 | $0.00758 |
| Sonnet 5.5 | $0.00013 | $0.00379 |
| Haiku 4.5 | $0.00006 | $0.00190 |
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 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 — 240 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(notController, 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 theRouteattribute 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
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 · 240 lines · 63 tokens per session scan A d88bd34f104f
csharp-api-controller-standards is a skill published in the GitHub repository linuxchata/ai-playbook (7 stars, last pushed 5mo ago), licensed MIT. It adds 63 tokens to every session and 1,896 once invoked, about $0.0003 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 skills, from other repositories
apideck-dotnet
Apideck Unified API integration patterns for C# and .NET. Use when building integrations with accounting software (QuickBooks, Xero, NetSuite), CRMs (Salesforce, HubSpot, Pipedrive), HRIS platforms (Workday, BambooHR), file storage (Google Drive, Dropbox, Box), ATS systems (Greenhouse, Lever), e-commerce, or any of…
csharp-developer
Use when building C# applications with .NET 8+, ASP.NET Core APIs, or Blazor web apps. Builds REST APIs using minimal or controller-based routing, configures database access with Entity Framework Core, implements async patterns and cancellation, structures applications with CQRS via MediatR, and scaffolds Blazor…
dotnet-core-expert
Use when building .NET 8 applications with minimal APIs, clean architecture, or cloud-native microservices. Invoke for Entity Framework Core, CQRS with MediatR, JWT authentication, AOT compilation.
aspnet-core
Guidelines for ASP.NET Core web development covering API design, authentication, caching, and best practices.
dotnet
Guidelines for .NET backend development with C#, ASP.NET Core, and Entity Framework Core.
123-java-design-patterns
Use when you need to select, review, or implement Java design and integration patterns — including classic Java design patterns, REST API patterns, Kafka and event-driven patterns, database and persistence patterns, and cross-cutting integration patterns. This should trigger for requests such as Apply Java design…