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/agentevalhq/agenteval/dotnet-inspectnpx skills add AgentEvalHQ/AgentEval --skill dotnet-inspectgit clone --depth 1 https://github.com/AgentEvalHQ/AgentEvalWhat 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.00054 | $0.04047 |
| Opus 5 | $0.00027 | $0.02024 |
| Sonnet 5 | $0.00011 | $0.00809 |
| Haiku 4.5 | $0.00005 | $0.00405 |
Grade A, and why
dotnet-inspect 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.
How it starts
The opening of the file, as written. The whole thing — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dotnet-inspect
Query .NET library APIs — the same commands work across NuGet packages, platform libraries (System., Microsoft.AspNetCore.), and local .dll/.nupkg files.
Quick Decision Tree
- Code broken? →
diff --package [email protected]first, thenmember - What's new in a .NET preview? →
diff --platform [email protected] --additiveper framework library - What types exist? →
type --package Foo(discover types in a package or library) - What members does a type have? →
member Type --package Foo(compact table by default) - What does a type look like? →
type Type --package Foo(tree view for single type) - What are the method signatures? →
member Type --package Foo -m Method(full signatures + docs) - What is the source/IL? →
member Type --package Foo -m Method:1 -v:d(Source, Lowered C#, IL) - Where is the source code? →
source Type --package Foo(SourceLink URLs),source Type -m Member(with line numbers) - Want raw source content? →
source Type --package Foo --cat(fetches and prints source files) - What constructors exist? →
member 'Type<T>' --package Foo -m .ctor(use<T>not<>) - How many overloads? →
member Type --package Foo --show-index(showsName:Nindices) - What does this package depend on? →
depends --package Foo - What does this type inherit? →
depends 'INumber<TSelf>' - Want a dependency diagram? →
depends --mermaid(standalone) ordepends --markdown --mermaid(embedded) - What metadata fields exist? →
-S Section --fields "PDB*"(structured query, no DSL) - What version is available? →
Foo --version(cache-first),Foo --latest-version(always NuGet),Foo --versions(list all)
When to Use This Skill
- "What types are in this package?" —
typediscovers types,findsearches by pattern - "What members does this type have?" —
memberfor methods/properties/events (docs on by default) - "What changed between versions?" —
diffclassifies breaking/additive changes - "What new APIs shipped in this preview?" —
diff --platform [email protected] --additiveper framework library - "This code uses an old API — fix it" —
diffthe old..new version, thenmemberto see the new API - "What extends this type?" —
extensionsfinds extension methods/properties (--reachablefor transitive) - "What implements this interface?" —
implementsfinds concrete types - "What does this type depend on?" —
dependswalks type hierarchy, package deps, or library refs - "Show dependencies as a diagram" —
depends --mermaidfor standalone mermaid,--markdown --mermaidfor embedded - "Where is the source code?" —
sourcereturns SourceLink URLs; add member name for line numbers - "What version/metadata does this have?" —
packageandlibraryinspect metadata - "What version is available?" —
Foo --version(fast, cache-first — likedocker run) - "What's the latest on NuGet?" —
Foo --latest-version(always queries NuGet — likedocker pull) - "What versions exist?" —
Foo --versions(list all published versions) - "What TFMs are available?" —
package Foo --tfms, thentype --package Foo --tfm net8.0 - "Where is the source code?" —
sourcereturns SourceLink URLs; add member name for line numbers - "Show me the actual source?" —
source Type --package Foo --catfetches and prints source file contents - "Show me something cool" —
demoruns curated showcase queries
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.
- 2d ago First seen · 266 lines · 54 tokens per session scan A 548bcc7b4d17
dotnet-inspect is a skill published in the GitHub repository AgentEvalHQ/AgentEval (138 stars, last pushed 2d ago), licensed MIT. It adds 54 tokens to every session and 4,047 once invoked, about $0.0003 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
smoke-test
End-to-end smoke test skill for DeerFlow. Guides through: 1) Pulling latest code, 2) Docker OR Local installation and deployment (user preference, default to Local if Docker network issues), 3) Service availability verification, 4) Health check, 5) Final test report. Use when the user says "run smoke test", "smoke…
image-generation
Use this skill when the user requests to generate, create, imagine, or visualize images including characters, scenes, products, or any visual content. Supports structured prompts and reference images for guided generation.
podcast-generation
Use this skill when the user requests to generate, create, or produce podcasts from text content. Converts written content into a two-host conversational podcast audio format with natural dialogue.
vercel-deploy
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.
skill-reviewer
Reviews DeerFlow skill packages for readiness, triggers, safety boundaries, resources, and evidence. Invoke when users ask to audit, grade, or production-check an existing skill.
surprise-me
Create a delightful, unexpected "wow" experience for the user by dynamically discovering and creatively combining other enabled skills. Triggers when the user says "surprise me" or any request expressing a desire for an unexpected creative showcase. Also triggers when the user is bored, wants inspiration, or asks for…