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 skills/stefanthecode/dotnet-ai-toolkit/healthchecks-setupnpx skills add StefanTheCode/dotnet-ai-toolkit --skill healthchecks-setupgit clone --depth 1 https://github.com/StefanTheCode/dotnet-ai-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/stefanthecode/dotnet-ai-toolkit/healthchecks-setup)<a href="https://agentmods.dev/skills/stefanthecode/dotnet-ai-toolkit/healthchecks-setup"><img src="https://agentmods.dev/badge/skills/stefanthecode/dotnet-ai-toolkit/healthchecks-setup.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.00101 | $0.00653 |
| Opus 5 | $0.00051 | $0.00327 |
| Sonnet 5 | $0.00020 | $0.00131 |
| Haiku 4.5 | $0.00010 | $0.00065 |
Grade A, and why
healthchecks-setup 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 4d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Health Checks Setup
Add health checks that orchestrators can actually use: a liveness probe (am I alive?) separate from a readiness probe (can I serve traffic?), with dependency checks tagged correctly.
Input — point it at your project
Works on a target: a project or GitHub URL. Inspect: grep -rn "AddHealthChecks\|MapHealthChecks\|UseHealthChecks" --include=*.cs <target> and the dependencies in .csproj (DB/cache/broker) to know what to check.
Wiring (the live/ready split that matters)
builder.Services.AddHealthChecks()
.AddNpgSql(conn, name: "db", tags: new[] { "ready" })
.AddRedis(redisConn, name: "redis", tags: new[] { "ready" })
.AddCheck("self", () => HealthCheckResult.Healthy(), tags: new[] { "live" });
// Liveness: is the process up? (no dependencies — don't restart on a DB blip)
app.MapHealthChecks("/health/live", new() { Predicate = c => c.Tags.Contains("live") });
// Readiness: can it serve? (include dependencies — pull from LB while a dep is down)
app.MapHealthChecks("/health/ready", new()
{
Predicate = c => c.Tags.Contains("ready"),
ResponseWriter = UIResponseWriter.WriteHealthCheckUIResponse // JSON detail
});
Kubernetes probes
livenessProbe: { httpGet: { path: /health/live, port: 8080 }, periodSeconds: 10 }
readinessProbe: { httpGet: { path: /health/ready, port: 8080 }, periodSeconds: 5 }
Principles
- Liveness ≠ readiness. Liveness must NOT depend on the DB — a transient DB outage shouldn't restart your pods. Readiness should, so traffic is withheld until dependencies recover.
- Keep checks fast and cheap (timeouts); a slow health check causes flapping.
- Don't expose detailed health publicly without auth — it leaks topology.
- Add a check per critical dependency, tagged
ready.
How to use it & best prompts
"Add health checks with liveness and readiness", "wire DB and Redis health", "Kubernetes probes for my service", "why does a DB blip restart my pods" (answer: liveness depends on DB — fix the split). Pairs with microservice-template-generator.
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.
- 4d ago First seen · 47 lines · 101 tokens per session scan A f6d2c4ed5b7f
healthchecks-setup is a skill published in the GitHub repository StefanTheCode/dotnet-ai-toolkit (19 stars, last pushed 25d ago), licensed MIT. It adds 101 tokens to every session and 653 once invoked, about $0.0005 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
otel-java
OpenTelemetry in Java — Javaagent zero-code instrumentation, Spring Boot Starter, manual autoconfigure SDK, declarative YAML configuration, BOM dependency management, sensitive-data capture and redaction (url.query, headers, request parameters, SQL sanitization). Use when adding, reviewing, or configuring…
frontmcp-production-readiness
Pre-production audit, hardening, and go-live checklists for FrontMCP servers. Use before shipping to verify security hardening, performance, reliability, and observability, and for target-specific production checklists: Node server (Docker, graceful shutdown, Redis session scaling), Vercel and edge (cold-start…
signoz-creating-dashboards
Create a new SigNoz dashboard from a natural-language intent: import a curated template (PostgreSQL, Redis, JVM, k8s, hostmetrics, APM, LLM, etc.) when one fits, or build a custom dashboard from scratch with metric / trace / log panels. Make sure to use this skill whenever the user says "create a dashboard for…", "set…
数据模型文档生成
当用户要生成或更新 Doris 表的数据模型 Markdown(三一级标题:数据摘要、数据表列、JSON扩展字段)、从 Doris 拉取元数据与至少 100 行样本,并由脚本或 --llm 补全说明时启用。.
setting-up-wide-events-store
Use when a human asks to set up, deploy, or finish deploying the bundled Wide Events DuckDB store (the Kamal accessory that receives production telemetry). Covers the store generator, DNS, kamal setup, and post-deploy verification end to end.
project-go-backend
Apply Go-specific patterns used in ai-viewer for fsnotify watching, SQLite access, SSE streaming, and structured logging. Use when editing internal/ingest, internal/store, internal/presenter, internal/adapters, internal/canonical, or internal/obs.