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 agentmods add skills/stefanthecode/dotnet-ai-toolkit/nuget-dependency-analyzernpx skills add StefanTheCode/dotnet-ai-toolkit --skill nuget-dependency-analyzergit 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/skills/stefanthecode/dotnet-ai-toolkit/nuget-dependency-analyzer)<a href="https://agentmods.dev/skills/stefanthecode/dotnet-ai-toolkit/nuget-dependency-analyzer"><img src="https://agentmods.dev/badge/skills/stefanthecode/dotnet-ai-toolkit/nuget-dependency-analyzer.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 | $0.00103 | $0.00599 |
| Opus 5 | $0.00051 | $0.00300 |
| Sonnet 5 | $0.00021 | $0.00120 |
| Haiku 4.5 | $0.00010 | $0.00060 |
Grade A, and why
nuget-dependency-analyzer 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 4d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NuGet Dependency Analyzer
Bring order to a multi-project solution's dependencies: spot version conflicts and drift, find unused/duplicate packages, and consolidate with Central Package Management.
Input — point it at your solution
Works on a target: a solution or GitHub URL. Map versions across projects:
find <target> -name "*.csproj" | xargs grep -h "PackageReference" | sort | uniq -c | sort -rn
dotnet list <target> package # per-project versions
dotnet list <target> package --outdated
What it finds
- Version drift — the same package pinned to different versions across projects (a top source of runtime binding surprises). Consolidate to one.
- Transitive conflicts — diamond dependencies resolved to a version no one intended.
- Unused packages — referenced but not used (check namespaces actually imported).
- Inconsistent meta-packages — mixing framework/package versions.
Central Package Management (CPM)
Recommend and scaffold Directory.Packages.props so versions live in one place:
<!-- Directory.Packages.props (repo root) -->
<Project>
<PropertyGroup><ManagePackageVersionsCentrally>true</ManagePackageVersionsCentrally></PropertyGroup>
<ItemGroup>
<PackageVersion Include="Serilog.AspNetCore" Version="10.0.0" />
<PackageVersion Include="FluentValidation" Version="11.11.0" />
</ItemGroup>
</Project>
Then .csproj files use <PackageReference Include="..." /> with no version — one source of truth.
Principles
- One version per package across the solution — drift causes the worst, hardest-to-repro bugs.
- CPM is the cure for version sprawl in multi-project repos.
- Remove what you don't use — fewer packages, smaller attack surface and faster restores.
- Pair with the vuln scanner: consolidation makes patching one place, not ten.
How to use it & best prompts
"Analyze my solution's NuGet dependencies", "fix version conflicts across projects", "set up Central Package Management", "find unused packages". Pairs with dependency-vuln-scanner.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 48 lines · 103 tokens per session scan A 7dab0072abdf
nuget-dependency-analyzer is a skill published in the GitHub repository StefanTheCode/dotnet-ai-toolkit (19 stars, last pushed 25d ago), licensed MIT. It adds 103 tokens to every session and 599 once invoked, about $0.0005 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…