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 agentmods add instructions/nanotaboada/dotnet.samples.aspnetcore.webapi/claude-mdgit clone --depth 1 https://github.com/nanotaboada/Dotnet.Samples.AspNetCore.WebApiWhat 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 | $0.01994 | $0.01994 |
| Opus 5 | $0.00997 | $0.00997 |
| Sonnet 5 | $0.00399 | $0.00399 |
| Haiku 4.5 | $0.00199 | $0.00199 |
Grade A, and why
Dotnet.Samples.AspNetCore.WebApi CLAUDE.md 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 3d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Overview
REST API for managing football players built with ASP.NET Core 10. Implements CRUD operations with a layered architecture, EF Core persistence (SQLite by default, PostgreSQL opt-in via DATABASE_PROVIDER), FluentValidation, AutoMapper, and in-memory caching. Primarily a learning and reference project — clarity and educational value take precedence over brevity.
Structure
Layer rule: Controller → Service → Repository → Database. Controllers must not access repositories directly. Business logic must not live in controllers.
Cross-cutting: Program.cs wires health checks (GET /health), rate limiting, CORS (dev only), and Swagger UI (dev only). Serilog is configured at host level. All validators are registered via AddValidatorsFromAssemblyContaining<PlayerRequestModelValidator>().
Coding Guidelines
- Naming: PascalCase (public members), camelCase (private fields with
_prefix) - DI: Primary constructors everywhere
- Async: All I/O operations use
async/await; noConfigureAwait(false)(unnecessary in ASP.NET Core) - Reads: Use
AsNoTracking()for all EF Core read queries - Errors: RFC 7807 Problem Details via
TypedResults.Problem(new HttpValidationProblemDetails(...))for validation failures (422) andTypedResults.Problem(statusCode: ...)for other errors - Logging: Structured logging via
ILogger<T>; neverConsole.Write - Avoid: synchronous EF Core APIs, controller business logic, static service/repository classes
Test naming conventions
Two naming patterns, strictly by layer:
| Layer | Location | Pattern | Example |
|---|---|---|---|
| Controller (unit) | test/.../Unit/ |
{HttpMethod}_{Resource}_{Condition}_Returns{Outcome} |
Get_Players_Existing_ReturnsPlayers |
| Service / Validator | test/.../Unit/ |
{MethodName}_{StateUnderTest}_{ExpectedBehavior} |
RetrieveAsync_CacheMiss_QueriesRepositoryAndCachesResult |
| HTTP integration | test/.../Integration/ |
{HttpMethod}_{Resource}_{Condition}_Returns{Outcome} |
Get_Players_Existing_Returns200Ok |
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.
- 3d ago First seen · 191 lines · 1,994 tokens per session scan A 15f4883ab5c2
Dotnet.Samples.AspNetCore.WebApi CLAUDE.md is an instructions file published in the GitHub repository nanotaboada/Dotnet.Samples.AspNetCore.WebApi (10 stars, last pushed 3d ago), licensed MIT. It adds 1,994 tokens to every session, about $0.0100 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.
Other instructions, from other repositories
go-samples-gin-restful CLAUDE.md
Instructions for nanotaboada/go-samples-gin-restful, covering claude.md, structure, coding guidelines, commands and quick start.
netrock CLAUDE.md
Instructions for fpindej/netrock, covering claude.md, hard rules, backend, frontend and cross-cutting.
python-samples-fastapi-restful CLAUDE.md
Instructions for nanotaboada/python-samples-fastapi-restful, covering claude.md, claude code, tech stack, structure and coding guidelines.
openresto CLAUDE.md
Claude Code instructions for karanshukla/openresto, covering claude.md, commands, run everything (recommended for local dev), backend only and frontend only.
FamilyNido CLAUDE.md
Instructions for pablitofernandez/FamilyNido, covering claude.md, c# development section start, c# instructions, general instructions and naming conventions.
phleet CLAUDE.md
Instructions for anurmatov/phleet, covering fleet — autonomous ai agent system, repository structure, build commands, build the entire solution and build a specific project.