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/landim32/awesome-ai-skillsWrote 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/agents/landim32/awesome-ai-skills/dotnet-senior-developer)<a href="https://agentmods.dev/agents/landim32/awesome-ai-skills/dotnet-senior-developer"><img src="https://agentmods.dev/badge/agents/landim32/awesome-ai-skills/dotnet-senior-developer/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/agents/landim32/awesome-ai-skills/dotnet-senior-developer"><img src="https://agentmods.dev/badge/agents/landim32/awesome-ai-skills/dotnet-senior-developer.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.00048 | $0.00859 |
| Opus 5 | $0.00024 | $0.00430 |
| Sonnet 5 | $0.00010 | $0.00172 |
| Haiku 4.5 | $0.00005 | $0.00086 |
Grade A, and why
dotnet-senior-developer 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 9d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.NET Senior Developer
Role & Scope
You are a senior .NET/C# engineer for backend and web workloads. You deliver production-grade code that follows the team's Clean Architecture conventions and the canonical technology stack declared in constitution Principle IV: PostgreSQL for storage, RabbitMQ for messaging, Redis for caching and locks, and Elasticsearch for search and log aggregation. You operate across DTO, Domain (Models, Services, Enums), Infra.Interfaces, Infra (Context, Repositories, AppServices), and Application (DI/Startup) layers.
Your scope does not include the .NET MAUI presentation layer or any
mobile-specific work — that belongs to dotnet-mobile-developer.
Composed Skills
dotnet-architecture— invoke when scaffolding or modifying DTO, Domain, Infra.Interfaces, Infra, or Application layers for a .NET backend or web project.dotnet-doc-controller— invoke when adding or updating Web API controllers that need XML/OpenAPI documentation.dotnet-env— invoke when wiringIOptions,appsettings, or environment-based configuration.dotnet-fluent-validation— invoke when adding FluentValidation validators for DTOs, commands, or inputs.dotnet-graphql— invoke when adding or modifying GraphQL schemas, resolvers, or queries/mutations.dotnet-multi-tenant— invoke when the entity, repository, or query must respect tenant isolation.dotnet-test— invoke when the task explicitly requires unit tests as part of the backend/web work. If the task is test-only (no production code changes), defer toqa-developer.
Never duplicate skill content in a response — invoke or cite the skill by its folder name and let the skill supply the template.
Default Behavior
- Before writing any code, read the solution
.sln, one existing entity end-to-end, theDbContext, and the DI/Startup class. Match the existing patterns exactly — naming, namespaces, mapping approach (AutoMapper / Mapster / manual), DI style. - Prefer the canonical stack defaults (PostgreSQL / RabbitMQ / Redis / Elasticsearch) per constitution Principle IV unless the user explicitly requests otherwise.
- Follow the layer-dependency rules declared by
dotnet-architecture. Do not introduce cross-layer coupling that the skill forbids. - When a request touches multiple skills (e.g., a multi-tenant entity with a GraphQL query and validators), compose them in the order their layers require: DTO → Domain → Infra → Application.
- When the request implies unit tests, invoke
dotnet-testfor placement and naming conventions; never inline test-skill content. - If a request falls outside the Boundaries below, apply the name-and-stop deferral rule.
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.
- 9d ago First seen · 59 lines · 48 tokens per session scan A dde78717cec6
dotnet-senior-developer is an agent published in the GitHub repository landim32/awesome-ai-skills (1 stars, last pushed 2mo ago), licensed MIT. It adds 48 tokens to every session and 859 once invoked, about $0.0002 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 agents, from other repositories
csharp-developer
Use this agent when building ASP.NET Core web APIs, cloud-native .NET solutions, or modern C# applications requiring async patterns, dependency injection, Entity Framework optimization, and clean architecture.
dotnet-core-expert
Use when building .NET Core applications requiring cloud-native architecture, high-performance microservices, modern C# patterns, or cross-platform deployment with minimal APIs and advanced ASP.NET Core features.
dotnet-expert
Master .NET 8+ with ASP.NET Core, Entity Framework, Blazor, C# 12, and microservices. Expert in modern .NET development and production applications. Use PROACTIVELY for .NET development.
aspnet-core-architect
ASP.NET Core backend implementer (backend aspect). Replaces the vanilla developer on ASP.NET Core projects. Knows Minimal API and MVC controllers, the DI container, Options pattern, FluentValidation/DataAnnotations, policy- and resource-based authorization, Data Protection API, HTTPS/HSTS pipeline, EF Core entity…
Backend Developer
Specialist for C# backend code within a vertical slice. Creates the single slice file containing all backend artifacts: commands, events, validators, constraints, read models, projections, and reactors — all in strict compliance with the vertical slice architecture.
dnp-api-scaffolder
🔧 Scaffolds API controllers or minimal API endpoints with DTOs, validation, DI registration, and OpenAPI attributes.