aspnetcore-security-auditor.USAGE

A security review agent for ASP.NET Core applications, the .NET framework used to build web APIs and websites. It checks code, configuration, authentication, access rules, dependencies, and other common risks against the OWASP Top 10, a widely used list of web security problems.

In plain words
What is it for?
Use it to review an ASP.NET Core repository, API, or solution before shipping, after adding authentication or endpoints, or when checking whether an application is secure.
Why use it?
It helps find security weaknesses before release or during regular reviews, including exposed secrets, unsafe settings, weak login protection, and missing access checks. Each result explains the possible attack and a suggested fix.

Agent

Install

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.

agentmods
npx agentmods add agents/stefanthecode/dotnet-ai-toolkit/aspnetcore-security-auditor.usage
Clone the repo
git clone --depth 1 https://github.com/StefanTheCode/dotnet-ai-toolkit
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 394 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00394
Opus 5 $0.00000 $0.00197
Sonnet 5 $0.00000 $0.00079
Haiku 4.5 $0.00000 $0.00039

Measured 2d ago against content hash 2916951b3fb3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

aspnetcore-security-auditor.USAGE 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 2d 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.

agents/aspnetcore-security-auditor.USAGE.md · 19 lines

What it actually says

How to use — ASP.NET Core Security Auditor (agent)

What it is. An agent that audits an ASP.NET Core codebase against the OWASP Top 10 and .NET-specific risks — broken access control, secrets in source, injection, insecure config, CORS, mass assignment, weak auth, vulnerable dependencies. It produces a risk-ranked report where every finding shows the vulnerable code, the concrete attack it enables, and the fix.

When to reach for it. A pre-release security pass, a periodic review, after adding auth or new endpoints, or "is my API actually secure".

How to use it. Point it at the repo/solution. It explores the attack surface itself (Program.cs, controllers, endpoints, appsettings, csproj). Example prompts:

  • "Run a security audit on this API."
  • "Check my ASP.NET Core app against the OWASP Top 10 before we ship."
  • "Are there any secrets or access-control gaps in this repo?"

How to get the best out of it.

  • Give it the full repo including config files — a lot of findings live in appsettings, CORS setup, and Program.cs, not just controllers.
  • Let it run dotnet list package --vulnerable (allow a restore) so the dependency-CVE check is real, not version-guessing.
  • Focus it if you want — "just access control and auth" — to get a deeper pass on one area.
  • Act on the Quick Wins section first — it's the highest-leverage subset.

What it won't do. It can't run the app, so some findings come marked "verify:" with how to confirm them. It's a code/config review, not a penetration test or DAST scan — treat it as the first line, not the only one. It won't invent vulnerabilities to pad the report.

Changes

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.

  1. 2d ago First seen · 19 lines · 0 tokens per session scan A 2916951b3fb3

Subscribe to this mod's changes

aspnetcore-security-auditor.USAGE is an agent published in the GitHub repository StefanTheCode/dotnet-ai-toolkit (19 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 394 tokens. 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.