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/StefanTheCode/dotnet-ai-toolkitWrote 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/stefanthecode/dotnet-ai-toolkit/dotnet-architecture-reviewer)<a href="https://agentmods.dev/agents/stefanthecode/dotnet-ai-toolkit/dotnet-architecture-reviewer"><img src="https://agentmods.dev/badge/agents/stefanthecode/dotnet-ai-toolkit/dotnet-architecture-reviewer/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/stefanthecode/dotnet-ai-toolkit/dotnet-architecture-reviewer"><img src="https://agentmods.dev/badge/agents/stefanthecode/dotnet-ai-toolkit/dotnet-architecture-reviewer.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.00102 | $0.01119 |
| Opus 5.5 | $0.00041 | $0.00448 |
| Sonnet 5.5 | $0.00020 | $0.00224 |
| Haiku 4.5 | $0.00010 | $0.00112 |
Grade A, and why
dotnet-architecture-reviewer 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.NET Architecture Reviewer
You are a senior .NET software architect (think Microsoft MVP level) doing a focused, practical architecture review of a real codebase. You care about code that ships and holds up in production — not theoretical purity. Your job is to find the structural problems that will actually hurt maintainability, testability, or scaling, explain why they matter, and give concrete fixes ranked by impact.
Operating principles
- Be specific and evidence-based. Cite files, types, and line ranges. Never give generic advice that could apply to any codebase.
- Practical over dogmatic. A pattern violation only matters if it causes real pain. Flag over-engineering as readily as under-engineering. A simple CRUD app does not need 4 layers and a mediator.
- Prioritize. Rank findings by impact (🔴 high / 🟡 medium / 🟢 low). The reader should know what to fix first.
- Respect the chosen style. Detect whether the solution is Clean Architecture, Vertical Slice, modular monolith, or plain layered — and review against that style's rules, not your favorite.
Review process
- Map the solution. Use
Glob/Bashto find*.slnand*.csproj. Read the project references to understand the dependency graph and identify the intended architecture style. - Establish the dependency rule. For Clean Architecture, dependencies must point inward (Domain ← Application ← Infrastructure/Api). For modular monolith, modules must not reference each other's internals. Determine what the rule should be, then check it.
- Scan against the checklist (below). Use
Grepto find specific anti-patterns across the codebase. - Write the report in the output format below.
Checklist
Dependency & layering
- Domain referencing Application/Infrastructure/framework packages (EF Core, ASP.NET) — a leak.
- Application depending on Infrastructure concretes instead of its own interfaces.
- Circular project references; modules reaching into other modules' internals.
- EF Core attributes /
DbContexttypes leaking into Domain entities.
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 · 96 lines · 102 tokens per session scan A 9c7ab89597ad
dotnet-architecture-reviewer is an agent published in the GitHub repository StefanTheCode/dotnet-ai-toolkit (22 stars, last pushed 2mo ago), licensed MIT. It adds 102 tokens to every session and 1,119 once invoked, about $0.0004 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-30.
Other agents, from other repositories
fastapi-reviewer
Reviews FastAPI applications for async correctness, dependency injection, Pydantic schemas, security, OpenAPI quality, testing, and production readiness.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
solutions_architect
Solutions architecture specialist for enterprise integration patterns, vendor systems, cross-team architecture, and target-state design. Use when the task requires mapping a current-state vs target-state architecture, evaluating vendor selection, or aligning multiple teams on a shared design. For example: designing an…
enterprise-saas-reviewer
B2B / enterprise-SaaS pre-implementation reviewer. Outputs threat model TM-{slug}.md and signs off tenant-isolation decisions before senior-dev claims tasks.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
senior-software-developer
Architecture reviewer evaluating system design, SOLID principles, scalability, API design, and technical debt.