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 Dannykkh/skill-olympus --skill dotnet-coding-standardsgit clone --depth 1 https://github.com/Dannykkh/skill-olympusWrote 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/dannykkh/skill-olympus/dotnet-coding-standards)<a href="https://agentmods.dev/skills/dannykkh/skill-olympus/dotnet-coding-standards"><img src="https://agentmods.dev/badge/skills/dannykkh/skill-olympus/dotnet-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/skills/dannykkh/skill-olympus/dotnet-coding-standards"><img src="https://agentmods.dev/badge/skills/dannykkh/skill-olympus/dotnet-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.00050 | $0.01718 |
| Opus 5.5 | $0.00020 | $0.00687 |
| Sonnet 5.5 | $0.00010 | $0.00344 |
| Haiku 4.5 | $0.00005 | $0.00172 |
Grade A, and why
dotnet-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 25d 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.NET Coding Standards - 통합 패키지
포함 파일
dotnet-coding-standards/
├── SKILL.md # 이 파일 (상세 코드 예시)
├── references/ # 핵심 규칙 (명시적 로드)
│ └── rules.md # 스킬 호출 시 읽는 규칙 본문
└── templates/ # 코드 템플릿 (on-demand)
├── csharp-patterns.md # Record DTO, Result, Pattern Matching, xUnit
├── aspnet-core.md # Program.cs, Minimal API, 미들웨어, JWT, Health
└── efcore-patterns.md # DbContext, DDD Entity, N+1, Migration, Audit
참조 로딩 규칙
- 이
SKILL.md를 워크플로와 예시의 소유자로 사용합니다. - 스킬을 명시적으로 호출했을 때
references/rules.md를 읽고 현재 프로젝트에 필요한 규칙만 적용합니다. - C# 일반 패턴, ASP.NET Core, EF Core 중 요청과 맞는
templates/파일만 추가로 읽습니다.
이 규칙 본문은 스킬 안의 참조 문서이며 커스텀 에이전트로 등록되지 않습니다.
Clean Architecture 코드 예시
Program.cs (최소 설정)
var builder = WebApplication.CreateBuilder(args);
// 서비스 등록 (Extension Method로 정리)
builder.Services.AddApplicationServices();
builder.Services.AddInfrastructureServices(builder.Configuration);
builder.Services.AddApiServices();
var app = builder.Build();
// 미들웨어 파이프라인
app.UseExceptionHandler();
app.UseAuthentication();
app.UseAuthorization();
// 엔드포인트 매핑
app.MapControllers();
// 또는 Minimal API:
// app.MapItemEndpoints();
app.Run();
DI 등록 (Extension Methods)
// Application/Extensions/ServiceCollectionExtensions.cs
public static class ApplicationServiceExtensions
{
public static IServiceCollection AddApplicationServices(this IServiceCollection services)
{
services.AddScoped<IItemService, ItemService>();
services.AddScoped<IOrderService, OrderService>();
services.AddValidatorsFromAssemblyContaining<ItemRequestValidator>();
return services;
}
}
// Infrastructure/Extensions/ServiceCollectionExtensions.cs
public static class InfrastructureServiceExtensions
{
public static IServiceCollection AddInfrastructureServices(
this IServiceCollection services, IConfiguration configuration)
{
services.AddDbContext<AppDbContext>(options =>
options.UseSqlServer(configuration.GetConnectionString("Default")));
services.AddScoped<IItemRepository, ItemRepository>();
services.AddMemoryCache();
return services;
}
}
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 25d ago Changed 72fd1e3e698d
- 1mo ago First seen · 258 lines · 50 tokens per session scan A 8550faf4587b
dotnet-coding-standards is a skill published in the GitHub repository Dannykkh/skill-olympus (7 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 1,718 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-09-03.
Other skills, from other repositories
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.
ddd
Domain-Driven Design patterns for .NET — aggregates, value objects, strongly-typed IDs, domain events, repositories, and the DDD variant of the layer rules.
vertical-slice
Vertical Slice Architecture (VSA) for .NET APIs — feature-first folder structure, IEndpointGroup pattern, cross-cutting concerns, and testing approach.
aspnet-api-patterns
ASP.NET Core API patterns — controllers vs minimal API, built-in OpenAPI, middleware order, IExceptionHandler + ProblemDetails, and Asp.Versioning.
clean-architecture
.NET clean architecture enforcement — layer rules, dependency direction, DI registration patterns, and project reference validation.