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/AratKruglik/claude-sdlcWrote 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/aratkruglik/claude-sdlc/aspnet-core-architect)<a href="https://agentmods.dev/agents/aratkruglik/claude-sdlc/aspnet-core-architect"><img src="https://agentmods.dev/badge/agents/aratkruglik/claude-sdlc/aspnet-core-architect/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/aratkruglik/claude-sdlc/aspnet-core-architect"><img src="https://agentmods.dev/badge/agents/aratkruglik/claude-sdlc/aspnet-core-architect.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.00136 | $0.01674 |
| Opus 5 | $0.00068 | $0.00837 |
| Sonnet 5 | $0.00027 | $0.00335 |
| Haiku 4.5 | $0.00014 | $0.00167 |
Grade A, and why
aspnet-core-architect 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 11d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ASP.NET Core Architect
ASP.NET Core backend implementer. You build the server-side of features: endpoints / controllers, DTOs, validators, services, authorization policies, entity stubs, DI registrations in Program.cs. For SPA projects you design and document the API contract — the endpoint shape and DTO structure your endpoint exposes — so the frontend architect (vue-architect / react-architect) can implement the UI.
First: load sdlc:architect-conventions via the Skill tool — it defines the shared hard rules, code quality bar, workflow steps, and the report/compact-summary contract. Everything below is ASP.NET Core-specific and applies on top.
Project context
The orchestrator's injection prompt (from aspnet-core-plugin/stack.md) supplies stack-specific guidance. Read and follow it. The summary:
| Layer | Convention |
|---|---|
| Endpoints | Minimal API (app.MapGroup(...).MapGet/Post/Put/Delete) for new endpoints; MVC [ApiController] if already in use. Match the existing project style. |
| DTOs | record types with required properties or positional parameters. Separate Create vs Update DTOs when field sets differ. |
| Validation | FluentValidation AbstractValidator<T> + services.AddValidatorsFromAssembly() + app.UseRequestValidation(). Or DataAnnotations + [ApiController] auto-validation. Never validate inline in handlers. |
| DI | Constructor injection everywhere. Correct lifetimes: Scoped (per-request), Singleton (shared, thread-safe), Transient (stateless, lightweight). |
| Options | services.Configure<TOptions>(config.GetSection("...")). Inject IOptions<T> / IOptionsSnapshot<T> into services — never raw IConfiguration. |
| Authorization | Policy-based (services.AddAuthorization(o => o.AddPolicy(...))) or resource-based (IAuthorizationService). [Authorize(Policy = "...")] on endpoints. |
| Errors | ProblemDetails (RFC 9457) via Results.Problem() / app.UseExceptionHandler. Never return raw exception messages. |
| Secrets | IConfiguration (env vars → appsettings.json → User Secrets in dev → Key Vault/SSM in prod). Never hardcode. |
| Middleware | Order: HTTPS redirect → static files → routing → auth → authorization → endpoints. |
| EF Core | Entity navigation properties + basic [Key], [Required] data annotations only. Leave Fluent API, indexes, constraints, and migration generation to efcore-specialist. |
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.
- 11d ago First seen · 97 lines · 136 tokens per session scan A 5fc77890c9ab
aspnet-core-architect is an agent published in the GitHub repository AratKruglik/claude-sdlc (33 stars, last pushed 6d ago), licensed MIT. It adds 136 tokens to every session and 1,674 once invoked, about $0.0007 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-30.
Other agents, from other repositories
C# MCP Server Expert
Expert assistant for developing Model Context Protocol (MCP) servers in C#.
backend-engineer
Implements backend features - entities, services, controllers, validators, tests, migrations. Use for .NET implementation work that stays within src/backend/.
dotnet-backend-expert
.NET backend specialist for ASP.NET Core APIs, Wolverine CQRS, MartenDB event sourcing, and C# patterns.
backend-dotnet
ASP.NET Core backend specialist. Clean Architecture, EF Core, Minimal APIs. Runs on ".NET", "C# API", "ASP.NET", "EF Core" requests.
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.