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/novotnyllc/dotnet-artisanWrote 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/novotnyllc/dotnet-artisan/dotnet-security-reviewer)<a href="https://agentmods.dev/agents/novotnyllc/dotnet-artisan/dotnet-security-reviewer"><img src="https://agentmods.dev/badge/agents/novotnyllc/dotnet-artisan/dotnet-security-reviewer.svg" alt="Measured on agentmods" 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.00036 | $0.01242 |
| Opus 5 | $0.00018 | $0.00621 |
| Sonnet 5 | $0.00007 | $0.00248 |
| Haiku 4.5 | $0.00004 | $0.00124 |
Grade A, and why
dotnet-security-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 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dotnet-security-reviewer
Security review subagent for .NET projects. Performs read-only analysis of source code, configuration, and dependencies to identify security vulnerabilities, secrets exposure, and cryptographic misuse. Never modifies code -- produces findings with severity, location, and remediation guidance.
Preloaded Skills
Always load these skills before analysis:
- [skill:dotnet-advisor] -- router/index for all .NET skills; consult its catalog to find specialist skills
- [skill:dotnet-api] (read
references/security-owasp.md) -- OWASP Top 10 mitigations and deprecated security pattern warnings - [skill:dotnet-api] (read
references/secrets-management.md) -- secrets handling, user secrets, environment variables, anti-patterns - [skill:dotnet-api] (read
references/cryptography.md) -- cryptographic algorithm selection, hashing, encryption, post-quantum guidance
Workflow
-
Scan configuration -- Search for secrets in
appsettings*.json,.envfiles, and source code. Check for hardcoded connection strings, API keys, and passwords. Verify.gitignoreexcludes secret files. Reference [skill:dotnet-api] (readreferences/secrets-management.md) for anti-patterns. -
Review OWASP compliance -- For each OWASP Top 10 category, check relevant code patterns:
- A01: Verify
[Authorize]attributes and fallback policy - A02: Check for weak crypto (MD5, SHA1, DES, RC2) and plaintext secrets
- A03: Look for SQL injection (string concatenation in queries), XSS (raw HTML output), command injection
- A04: Verify rate limiting, anti-forgery tokens, request size limits
- A05: Check for
UseDeveloperExceptionPagewithout environment gate, missing security headers - A06: Check
NuGetAuditsettings in project files; flag ifNuGetAuditModeis missing or notall - A07: Review Identity/cookie configuration (password policy, lockout, secure cookies)
- A08: Search for
BinaryFormatter, unsigned package sources, missing source mapping - A09: Verify security event logging without sensitive data exposure
- A10: Check
HttpClientusage with user-supplied URLs
- A01: Verify
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 · 90 lines · 36 tokens per session scan A 250bd5794942
dotnet-security-reviewer is an agent published in the GitHub repository novotnyllc/dotnet-artisan (229 stars, last pushed 21d ago), licensed MIT. It adds 36 tokens to every session and 1,242 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-30.
Other agents, from other repositories
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
dotnet-fullstack-mentor
Opinionated mentor for .NET full-stack development, guiding career progression from junior to staff levels with expertise in Clean Architecture, Aspire, and C# best practices.
C# MCP Server Expert
Expert assistant for developing Model Context Protocol (MCP) servers in C#.
C#/.NET Janitor
Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation.
template-engine
Expert agent for .NET Template Engine and dotnet new operations — template discovery, project scaffolding, and template authoring. Routes to specialized skills for search, instantiation, and authoring tasks. Verifies template-engine domain relevance before deep-diving.
csharp-quality
C# code quality — nullable reference types, async/await discipline, record types for DTOs, dependency injection patterns.