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.
npx skills add CartapenaBark/DotNetAnalyzer --skill dotnet-analyzer-security-depsgit clone --depth 1 https://github.com/CartapenaBark/DotNetAnalyzerWrote 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/skills/cartapenabark/dotnetanalyzer/dotnet-analyzer-security-deps)<a href="https://agentmods.dev/skills/cartapenabark/dotnetanalyzer/dotnet-analyzer-security-deps"><img src="https://agentmods.dev/badge/skills/cartapenabark/dotnetanalyzer/dotnet-analyzer-security-deps/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/skills/cartapenabark/dotnetanalyzer/dotnet-analyzer-security-deps"><img src="https://agentmods.dev/badge/skills/cartapenabark/dotnetanalyzer/dotnet-analyzer-security-deps.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.00227 | $0.01020 |
| Opus 5 | $0.00113 | $0.00510 |
| Sonnet 5 | $0.00045 | $0.00204 |
| Haiku 4.5 | $0.00023 | $0.00102 |
Grade A, and why
dotnet-analyzer-security-deps 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.NET Security and Dependency Analysis
Scan .NET projects for security vulnerabilities and dependency health issues.
Prerequisite Check
Before any analysis, verify dotnet-analyzer is installed:
- Run
dotnet-analyzer --versionin a shell - If it fails, ask the user: "DotNetAnalyzer global tool is not installed. Shall I run
dotnet tool install --global DotNetAnalyzerfor you?"- If confirmed, run the install command and continue
- If declined, provide the manual install command and stop
Available MCP Tools
Use these MCP tools (prefixed with mcp__plugin_netan_dotnet-analyzer__):
| Tool | Purpose | Key Parameters |
|---|---|---|
scan_security_vulnerabilities |
OWASP Top 10 security scan | projectPath, optional severity |
generate_security_sarif |
Security SARIF v2.1.0 report | projectPath |
get_security_rules |
List registered security rules | (no parameters) |
check_license_compliance |
License whitelist compliance | projectPath, optional allowedLicenses |
scan_nuget_vulnerabilities |
CVE scan via NuGet.org API | projectPath |
scan_dependencies_health |
Overall dependency health score | projectPath |
detect_dependency_conflicts |
Cross-project version conflicts | solutionPath |
Security Detection Rules
| Rule ID | Rule Name | OWASP Category | CWE |
|---|---|---|---|
| SEC001 | Hardcoded Credentials | A02:2021 - Cryptographic Failures | CWE-798 |
| SEC002 | SQL Injection | A03:2021 - Injection | CWE-89 |
| SEC003 | Command Injection | A03:2021 - Injection | CWE-78 |
| SEC004 | Unsafe Deserialization | A08:2021 - Software Integrity | CWE-502 |
| SEC005 | Path Traversal | A01:2021 - Broken Access Control | CWE-22 |
| SEC006 | XSS Detection | A03:2021 - Injection | CWE-79 |
Workflow
Security Scan
- Scan vulnerabilities: Call
scan_security_vulnerabilitieswithseverity: "Medium" - Generate SARIF: Call
generate_security_sariffor GitHub Code Scanning integration - Present: Group findings by severity (Critical > High > Medium > Low)
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 · 91 lines · 227 tokens per session scan A 57a48622676b
dotnet-analyzer-security-deps is a skill published in the GitHub repository CartapenaBark/DotNetAnalyzer (2 stars, last pushed 4mo ago), licensed MIT. It adds 227 tokens to every session and 1,020 once invoked, about $0.0011 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.
Other skills, from other repositories
ch015-feedback
Run CH015 security design review workflows for PRDs and specs to produce security opinions or review findings mapped to standards and regulatory requirements.
ch015
Run CH015 AI Security Firm workflows for security audits, vulnerability assessment, adversarial verification, pentesting, red team review, compliance checks, fix guidance, and report generation.
Event-Driven Semantics & Delivery Guarantees
Ensure event-driven designs specify delivery guarantees, ordering, idempotency, schema evolution, and replay/backfill strategy.
External Dependencies & Vendor Risks
Ensure designs document third-party dependencies, SLAs, quotas, failure modes, and vendor lock-in mitigation.
Trust Boundaries & Authorization Architecture
Ensure designs define trust boundaries, authn/authz responsibilities, and propagation of identity/claims across services.
dist-design
This skill should be used when choosing between architectural options for how independently-deployed processes or services will communicate, share state, or scale — stream vs. queue vs. RPC, splitting a monolith into services, a replication/partitioning strategy, or cross-service retry and circuit-breaker design. Runs…