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 darylmcd/Roslyn-Backed-MCP --skill project-inspectiongit clone --depth 1 https://github.com/darylmcd/Roslyn-Backed-MCPWrote 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/darylmcd/roslyn-backed-mcp/project-inspection)<a href="https://agentmods.dev/skills/darylmcd/roslyn-backed-mcp/project-inspection"><img src="https://agentmods.dev/badge/skills/darylmcd/roslyn-backed-mcp/project-inspection/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/darylmcd/roslyn-backed-mcp/project-inspection"><img src="https://agentmods.dev/badge/skills/darylmcd/roslyn-backed-mcp/project-inspection.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.00038 | $0.00892 |
| Opus 5 | $0.00019 | $0.00446 |
| Sonnet 5 | $0.00008 | $0.00178 |
| Haiku 4.5 | $0.00004 | $0.00089 |
Grade A, and why
project-inspection 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 11d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MSBuild / Project Inspection
You answer "what does MSBuild think this project is?" using evaluate_msbuild_property, evaluate_msbuild_items, and get_msbuild_properties.
Input
Resolve:
workspaceId(active session)- Absolute
projectFilePath(.csprojor relevant project file) - Optionally a single property name (e.g.
TargetFramework) or item type (e.g.PackageReference)
Server discovery
Use roslyn://server/catalog under project-mutation / configuration. MCP prompt msbuild_inspection emits a checklist for this workspace + project path.
Workflow
- Confirm the workspace is loaded and the path is the project the user cares about (SDK-style vs legacy).
- For one or two values:
evaluate_msbuild_property. - For item lists:
evaluate_msbuild_itemswith the item type. - For a broad dump:
get_msbuild_properties(large — filter to what matters). - If project files changed on disk:
workspace_reloadbefore trusting compilation or symbol tools.
Validate project shape
Invoke with --validate-shape or ask "is this project set up right?". The skill runs a consistency sweep over one project (or every project in the workspace) and flags common defaults-drift.
For each project, check:
| Check | Default expected | Signal when missing/inconsistent |
|---|---|---|
TargetFramework / TargetFrameworks |
Present; matches solution-wide convention when one exists | Orphan or legacy TFM (e.g., net462 in a mostly-net8.0 solution) |
Nullable |
enable recommended for new code |
disable or missing on a library in an otherwise-nullable solution |
ImplicitUsings |
enable for SDK-style projects |
Missing / disabled |
LangVersion |
Implicit (inherits from TFM) | Pinned to an old version (latest or a specific version below what TFM allows) |
TreatWarningsAsErrors |
Typically true for production libraries |
Missing in a library where siblings enable it |
GenerateDocumentationFile |
true for packable libraries |
Missing when IsPackable=true |
IsPackable |
false for test/sample projects |
true on a project whose name ends .Tests / .Samples |
OutputType |
Library by default; Exe only for hosts |
Exe in a project consumed as a package dependency |
RootNamespace vs folder path |
Aligned | Drift (package extracts from a folder that doesn't match namespace) |
AssemblyName vs PackageId (packable) |
Typically equal | Divergent without explicit intent |
| Project references in SDK-style | Use <ProjectReference> |
Direct <Reference> assembly paths indicate legacy style |
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.
- 11d ago First seen · 65 lines · 38 tokens per session scan A ebc900a823b9
project-inspection is a skill published in the GitHub repository darylmcd/Roslyn-Backed-MCP (1 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 892 once invoked, about $0.0002 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
dotnet-reverse
A guide for analyzing compiled .NET and C# programs, including managed Windows executables and libraries. Reverse engineering means studying compiled software to understand how it works, and decompiling turns it back into readable approximate source code.
check-bin-obj-clash
Detects MSBuild projects with conflicting OutputPath or IntermediateOutputPath. USE FOR: builds failing with 'Cannot create a file when that file already exists', 'The process cannot access the file because it is being used by another process', intermittent build failures that succeed on retry, or missing/overwritten…
build-perf-diagnostics
Diagnose MSBuild build performance bottlenecks using binary log analysis. USE FOR: identifying why builds are slow by analyzing binlog performance summaries, detecting ResolveAssemblyReference (RAR) taking >5s, Roslyn analyzers consuming >30% of Csc time, single targets dominating >50% of build time, node utilization…
dump-collect
Configure and collect crash dumps for modern .NET applications. USE FOR: enabling automatic crash dumps for CoreCLR or NativeAOT, capturing dumps from running .NET processes, setting up dump collection in Docker or Kubernetes, using dotnet-dump collect or createdump. DO NOT USE FOR: analyzing or debugging dumps…
binlog-generation
Generate MSBuild binary logs (binlogs) for build diagnostics and analysis. USE FOR: adding /bl:{} to any dotnet build, test, pack, publish, or restore command to capture a full build execution trace, prerequisite for binlog-failure-analysis and build-perf-diagnostics skills, enabling post-build investigation of errors…
binlog-failure-analysis
Analyze MSBuild binary logs to diagnose build failures. USE FOR: build errors that are unclear from console output, diagnosing cascading failures across multi-project builds, tracing MSBuild target execution order, and generally any MSBuild build issues. Requires an existing .binlog file. DO NOT USE FOR: generating…