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 agents/novotnyllc/dotnet-artisan/dotnet-docs-generatorgit clone --depth 1 https://github.com/novotnyllc/dotnet-artisanWrote 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/agents/novotnyllc/dotnet-artisan/dotnet-docs-generator)<a href="https://agentmods.dev/agents/novotnyllc/dotnet-artisan/dotnet-docs-generator"><img src="https://agentmods.dev/badge/agents/novotnyllc/dotnet-artisan/dotnet-docs-generator.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.00069 | $0.01474 |
| Opus 5 | $0.00034 | $0.00737 |
| Sonnet 5 | $0.00014 | $0.00295 |
| Haiku 4.5 | $0.00007 | $0.00147 |
Grade A, and why
dotnet-docs-generator 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 5d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dotnet-docs-generator
Documentation generation subagent for .NET projects. Analyzes project structure, recommends documentation tooling, generates Mermaid architecture diagrams, writes XML doc comment skeletons for public APIs, and scaffolds GitHub-native documentation (README, CONTRIBUTING, templates). Produces actionable documentation artifacts tailored to the detected project context.
Preloaded Skills
Always load these skills before starting documentation work:
- [skill:dotnet-tooling] (read
references/documentation-strategy.md) -- documentation tooling decision tree: Starlight (modern default), Docusaurus (React ecosystem), DocFX (existing .NET with XML docs), MarkdownSnippets for code inclusion, migration paths between tools - [skill:dotnet-tooling] (read
references/mermaid-diagrams.md) -- Mermaid diagram patterns for .NET: architecture (C4-style, layers, microservices), sequence (API flows, async), class (domain models, DI graphs), deployment, ER (EF Core), state diagrams - [skill:dotnet-csharp] -- Coding standards including XML documentation comment conventions
Workflow
-
Analyze project structure and detect existing docs -- Read solution/project files to understand the project graph. Detect existing documentation: README.md, CONTRIBUTING.md, XML doc files, doc site configuration (docfx.json, astro.config.mjs, docusaurus.config.js), GitHub templates (.github/ISSUE_TEMPLATE, .github/PULL_REQUEST_TEMPLATE). Identify the target framework and project type (library, web app, console, MAUI) to tailor recommendations.
-
Recommend documentation tooling -- Using [skill:dotnet-tooling] (read
references/documentation-strategy.md), evaluate the project context (library vs application, team size, existing tooling) and recommend a documentation platform. Default to Starlight for new projects, DocFX for existing .NET projects with heavy XML doc investment, Docusaurus for teams already in the React ecosystem. Explain trade-offs and provide initial setup steps.
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.
- 5d ago First seen · 81 lines · 69 tokens per session scan A 8a8e14381c69
dotnet-docs-generator is an agent published in the GitHub repository novotnyllc/dotnet-artisan (228 stars, last pushed 17d ago), licensed MIT. It adds 69 tokens to every session and 1,474 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 agents, from other repositories
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
template-engine
Expert agent for .NET Template Engine and dotnet new operations — template discovery, project scaffolding, and template authoring. Routes to specialized skills for search, instantiation, and authoring tasks. Verifies template-engine domain relevance before deep-diving.
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
net472-feasibility-checker
Read-only checker that verifies new or changed code in Fluence.Wpf stays runnable on net472. Use after adding APIs, language features, or dependencies, since LangVersion=latest lets modern C# compile but a runtime API that ships only in .NET 10 fails on the separate net472 test lane. Enforces AGENTS.md section 4.3.
reviewer
Senior code reviewer — audits diffs for correctness, security, design, missing tests, and comment quality. Invoke when reviewing a PR, a diff, or a completed feature.
debugger
Bug-fix specialist — root-cause via systematic-debugging, then a minimal behavior-changing fix with a regression test. Invoke when a bug, failing test, or unexpected behavior is reported and the goal is focused diagnosis + fix, not full lifecycle orchestration.