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 Attemainio/dotnet-toolkit --skill dotnet-exploregit clone --depth 1 https://github.com/Attemainio/dotnet-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/attemainio/dotnet-toolkit/dotnet-explore)<a href="https://agentmods.dev/skills/attemainio/dotnet-toolkit/dotnet-explore"><img src="https://agentmods.dev/badge/skills/attemainio/dotnet-toolkit/dotnet-explore/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/attemainio/dotnet-toolkit/dotnet-explore"><img src="https://agentmods.dev/badge/skills/attemainio/dotnet-toolkit/dotnet-explore.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.00104 | $0.01333 |
| Opus 5.5 | $0.00042 | $0.00533 |
| Sonnet 5.5 | $0.00021 | $0.00267 |
| Haiku 4.5 | $0.00010 | $0.00133 |
Grade A, and why
dotnet-explore 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 1mo 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delegating the sweep to dotnet-explore
This plugin ships one read-only navigator subagent, dotnet-explore. It turns a prose task into the
symbols it is about: symbolIds, use sites, affected files, and how far a change would reach. It
never judges code and it cannot change it — the invoking agent decides what to do with the map.
Host adapter
Claude Code can launch the bundled dotnet-explore custom agent directly. Codex plugins do not
currently install custom-agent registrations. In Codex, launch the built-in read-only explorer and
start its brief with: "Read <pluginRoot>/agents/dotnet-explore.md and follow its Markdown body;
ignore only the Claude-specific YAML frontmatter." The file under agents/ remains the one role
contract; do not copy its body into this skill or a Codex-only agent file.
Why delegate rather than fan out yourself. A wide search_index plus a get_references per
candidate is the single most expensive shape of read this server produces, and almost all of those
tokens are scaffolding you throw away once you know the answer. The agent pays them in its own
context and returns a report a fraction of the size.
When to invoke it — and when not to
Invoke it when the symbol set is genuinely unknown: an unfamiliar subsystem, "how would this feature land", "what breaks if I change this", a review or refactor whose boundary you cannot yet name.
Skip it when:
- The symbol is already known. A two-call lookup is not what this is for; use
dotnet-read. - You need the text, not the map. The agent never reads a
.csfile; it reportsdeclarationSites, and the rangedReadover them is yours to make. - The answer is in a non-C# file.
.csproj,.json,.md,.editorconfigare out of its scope; it will say so and stop.
Step 0 — check readiness before launching
Call workspace_status yourself, before spawning. The agent checks too, but a cold or degraded
workspace wastes an entire agent run:
- Still loading, or
index_only→ semantic results are unavailable, not empty. Wait, or accept a syntax-tier map and say so. degraded(projects failed to load) → the map may be silently wrong. Fix the build andreload_workspacebefore spawning, or don't spawn.- Just did a
git pull/checkout/rebase, or added or deleted a.csfile →reload_workspace(scope: "all")first.
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.
- 1mo ago Changed · -1 lines 1f36eb2a3bab
- 1mo ago Changed · +13 lines · +104 tokens per session 71f4bfd088f8
- 1mo ago First seen · 88 lines · 0 tokens per session scan A 769809951cfe
dotnet-explore is a skill published in the GitHub repository Attemainio/dotnet-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 104 tokens to every session and 1,333 once invoked, about $0.0004 per session on Opus 5.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
rider-search
Routing rules for code search in JetBrains Rider projects — use the Rider MCP symbol/reference/file tools instead of Bash grep. Use whenever searching for a symbol, definition, function, variable, type, or finding usages/references in a C#/.NET or Unreal C++ codebase open in Rider.
bootstrap-solution
Bootstrap or guide a reproducible .NET solution with explicit F# or C# language choice, SDK selection, project layout, test project setup, and initial validation commands.
build-csharp-project
Build or modify idiomatic C# .NET projects using nullable-aware APIs, records/classes, async/task behavior, analyzer conventions, tests, and repo-local validation.
grasshopper-component
Complete guide for developing custom Grasshopper components in C# — GHComponent class, RegisterInputParams/OutputParams, SolveInstance, DataTree patterns, parameter types, error handling, and component packaging as .gha. Use this skill whenever creating or debugging a Grasshopper component: "grasshopper component c#"…
rhinocommon-geometry
Deep reference for Rhino.Geometry namespace — all geometry types, operations, and patterns in RhinoCommon. Use this skill whenever working with Rhino geometry in C# or Python: Point3d, Vector3d, Curve, Surface, Brep, Mesh, NURBS, intersections, boolean operations, transforms, planes, bounding boxes. Triggers on…
dotnet-analyzer-code-intelligence
Navigate and understand C# code through symbol queries, type hierarchies, call graphs, and semantic analysis using Roslyn-powered MCP tools. Use when the user asks to find references, go to definition, understand type inheritance, explore call hierarchies, get symbol info, analyze code metrics, or traverse syntax…