security

A .NET security and dependency checker. Dependencies are third-party packages your project uses; CVEs are publicly reported security flaws in software.

In plain words
What is it for?
Use it to scan a .NET project or solution for OWASP Top 10 risks, CVEs, outdated dependencies, and license-compliance issues.
Why use it?
It helps reveal security weaknesses and unhealthy packages before they become deployment or maintenance problems. It also checks whether packages are outdated or have licensing concerns.

Command

Part of the netan plugin — 5 skills, 3 commands shipped together

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 commands/cartapenabark/dotnetanalyzer/security
Clone the repo
git clone --depth 1 https://github.com/CartapenaBark/DotNetAnalyzer

Or install netan, the plugin that ships this one along with the rest of its 5 skills, 3 commands.

Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 654 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.00014 $0.00654
Opus 5 $0.00007 $0.00327
Sonnet 5 $0.00003 $0.00131
Haiku 4.5 $0.00001 $0.00065

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

Security

Grade A, and why

security 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.

plugin/commands/security.md · 82 lines

How it starts

The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/netan:security — .NET Security Scan

Scan a .NET project for security vulnerabilities (OWASP Top 10) and dependency health issues (CVE, outdated packages, license compliance).

Prerequisite Check

  1. Run dotnet-analyzer --version to verify the global tool is installed
  2. If it fails, ask the user: "DotNetAnalyzer global tool is not installed. Shall I run dotnet tool install --global DotNetAnalyzer for you?"
    • If confirmed, run dotnet tool install --global DotNetAnalyzer and continue
    • If declined, provide the manual install command and stop

Arguments

The user may optionally provide a project or solution path:

  • If provided: use that path directly
  • If not provided: auto-detect by looking for *.slnx or *.sln in the current working directory
  • If no solution file found: ask the user for the path

Steps

  1. Identify the target:

    • Use the provided path, or auto-detect *.slnx / *.sln in the current directory
    • Prefer solution file for comprehensive scanning
  2. Scan security vulnerabilities:

    • Call scan_security_vulnerabilities with the project path
    • Use minimum severity Medium (default) unless user specifies otherwise
  3. Scan dependency health:

    • Call scan_dependencies_health with the project path
    • Note overall health score, outdated packages, deprecated packages
  4. Check license compliance:

    • Call check_license_compliance with the project path
    • Report any non-compliant packages
  5. Present findings grouped by severity:

    ## Security Scan: [Project/Solution Name]
    
    ### Overview
    - Total findings: N
    - Critical: N | High: N | Medium: N | Low: N
    
    ### Critical / High Severity
    | Rule | Finding | File | Fix |
    |------|---------|------|-----|
    | SEC001 | Hardcoded credential | ... | ... |
    
    ### Medium Severity
    | Rule | Finding | File | Fix |
    |------|---------|------|-----|
    | ... | ... | ... | ... |
    
    ### Dependency Health
    - Health Score: N/100
    - Outdated: N packages
    - Vulnerable: N packages
    - Deprecated: N packages
    
    ### License Issues
    - Non-compliant: N packages
    | Package | License | Issue |
    |---------|---------|-------|
    | ... | GPL-3.0 | Not in whitelist |
    
    ### Recommendations
    - [Prioritized action items]
    

Read the full file on GitHub · 82 lines

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 · 82 lines · 14 tokens per session scan A 37d491b8c36d

Subscribe to this mod's changes

security is a command published in the GitHub repository CartapenaBark/DotNetAnalyzer (2 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 654 once invoked, about $0.0001 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-31.