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 codewithmukesh/dotnet-claude-kit --skill health-checkgit clone --depth 1 https://github.com/codewithmukesh/dotnet-claude-kitWrote 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/codewithmukesh/dotnet-claude-kit/health-check)<a href="https://agentmods.dev/skills/codewithmukesh/dotnet-claude-kit/health-check"><img src="https://agentmods.dev/badge/skills/codewithmukesh/dotnet-claude-kit/health-check.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00115 | $0.01568 |
| Opus 5 | $0.00057 | $0.00784 |
| Sonnet 5 | $0.00023 | $0.00314 |
| Haiku 4.5 | $0.00012 | $0.00157 |
Grade A, and why
health-check 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 8d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/health-check — 8-Dimension Project Assessment
What
Runs a data-driven health assessment across 8 dimensions, each graded A-F with the specific data points that produced the grade, and rolls them into a GPA. Gut feeling is not a grade: every dimension uses MCP tools or CLI commands, and every grade below A comes with specific, prioritized, effort-estimated fixes — "add test classes for OrderService, PaymentProcessor, ShippingCalculator" is actionable; "improve test coverage" is not.
This skill owns the canonical grading system for the kit. The full rubrics,
GPA scale, and report template live in references/grading-rubric.md — load
that file when running an assessment.
Tone is diagnostic, not punitive: a C grade is an improvement path, not a failure.
When
- Onboarding to an unfamiliar or new project — set the baseline
- "How healthy is this?", "grade this project", "codebase review", "report card"
- Pre-release quality gate, or monthly/quarterly maintenance review
- After a cleanup sprint (
/de-sloppify) — re-grade to show progress - Tech-debt prioritization — lowest grades get the next sprint's attention
How
Step 1: Choose Scope
| Scenario | Dimensions |
|---|---|
| Full assessment (onboarding, pre-release, monthly review) | All 8 |
| Quick health (mid-sprint checkpoint, before a demo, after a merge) | 1-4 only |
| After major refactor | 1 (Build), 3 (Architecture), 4 (Tests) |
| Post-dependency update | 1 (Build), 7 (Security) |
| After cleanup sprint | Re-grade only the cleaned dimensions |
Step 2: Run the Dimensions
Read references/grading-rubric.md for the grade thresholds, then collect data
per dimension. For deep code-quality dimensions, delegate to the
code-reviewer agent with the code-review skill.
| # | Dimension | Data source |
|---|---|---|
| 1 | Build Health | dotnet build --no-restore — errors + warnings |
| 2 | Code Quality | MCP detect_antipatterns — read summary, grade high-confidence only |
| 3 | Architecture | MCP get_project_graph + detect_circular_dependencies (projects AND types) |
| 4 | Test Coverage | MCP get_test_coverage_map — check applicable first (structural, not line coverage) |
| 5 | Dead Code | MCP find_dead_code(scope: "solution") — grade high-confidence; ignore conventionFiltered |
| 6 | API Surface | MCP get_public_api + find_references — overexposure, return-type consistency |
| 7 | Security Posture | dotnet list package --vulnerable --include-transitive + secrets/auth spot check (deep dive: /security-scan) |
| 8 | Documentation | XML doc coverage on public APIs + README currency |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 136 lines · 115 tokens per session scan A 2a6ba1a934dd
health-check is a skill published in the GitHub repository codewithmukesh/dotnet-claude-kit (699 stars, last pushed 1mo ago), licensed MIT. It adds 115 tokens to every session and 1,568 once invoked, about $0.0006 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.