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.
git 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/plugins/cartapenabark/dotnetanalyzer/marketplace)<a href="https://agentmods.dev/plugins/cartapenabark/dotnetanalyzer/marketplace"><img src="https://agentmods.dev/badge/plugins/cartapenabark/dotnetanalyzer/marketplace/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/plugins/cartapenabark/dotnetanalyzer/marketplace"><img src="https://agentmods.dev/badge/plugins/cartapenabark/dotnetanalyzer/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dotnet-analyzer marketplace 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.
What it actually says
{
"name": "dotnet-analyzer",
"owner": {
"name": "CartapenaBark"
},
"plugins": [
{
"name": "dotnet-analyzer",
"description": "DotNetAnalyzer — 93 MCP tools for .NET code analysis, refactoring, security scanning, and architecture checking via Roslyn",
"source": {
"source": "git-subdir",
"url": "CartapenaBark/DotNetAnalyzer",
"path": "plugin"
},
"homepage": "https://github.com/CartapenaBark/DotNetAnalyzer"
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
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 First seen · 19 lines scan A 7ae43d78047d
dotnet-analyzer marketplace is a plugin published in the GitHub repository CartapenaBark/DotNetAnalyzer (2 stars, last pushed 6mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
roslyn-codelens
Roslyn-based code graph intelligence for .NET codebases. Requires the .NET 10 SDK; the server is fetched and run on demand via dnx.
roslyn-mcp
Roslyn-powered C# refactoring MCP server — 50 tools for code navigation, analysis, generation, and refactoring across entire .NET solutions.
dekko
Static code map for LLM agents. /map parses the repository with tree-sitter into MAP.md and map.json (every file, function, signature, type, and call edge) without spending model tokens; an 18-tool MCP server (searchcode, outline, querysymbol, getcallers, workset, impactedtests, ...) answers structural questions fr.
pharaoh
Codebase knowledge graph with focused development workflow skills. Query architecture, dependencies, blast radius, and more instead of reading files one at a time.
capstone
Architecture reference generator: a lean docs/capstone/ index plus topic files stamped to the commit they were derived at, built and kept current by one command, map. Companion commands: doctor, an opt-in two-sided review, a greenfield pipeline from mockup to running code with a frontend-design stage, and a…
capstone
Architecture reference docs: a docs/capstone/ index plus topic files stamped to commits, built and kept current by one command, map, plus doctor/review, a greenfield pipeline from product mockup to running code with a frontend-design stage, and a doc-grounded feature chain.