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 soulcodex/agentic --skill health-check-endpointsgit clone --depth 1 https://github.com/soulcodex/agenticWrote 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/soulcodex/agentic/health-check-endpoints)<a href="https://agentmods.dev/skills/soulcodex/agentic/health-check-endpoints"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/health-check-endpoints/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/soulcodex/agentic/health-check-endpoints"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/health-check-endpoints.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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.00058 | $0.01192 |
| Opus 5.5 | $0.00023 | $0.00477 |
| Sonnet 5.5 | $0.00012 | $0.00238 |
| Haiku 4.5 | $0.00006 | $0.00119 |
Grade A, and why
health-check-endpoints 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.
How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Health Check Endpoints Skill
Step 1 — Liveness Endpoint
GET /health/live
Purpose: tells Kubernetes whether the process is alive. If this fails, the pod is restarted. Do not check external dependencies here — a database outage should not restart all pods.
// Go example
func livenessHandler(w http.ResponseWriter, r *http.Request) {
w.Header().Set("Content-Type", "application/json")
w.WriteHeader(http.StatusOK)
json.NewEncoder(w).Encode(map[string]string{"status": "ok"})
}
Rules:
- Always returns
200 OKunless the process is deadlocked or terminally broken. - No database, cache, or broker calls.
- Response time < 5 ms.
Step 2 — Readiness Endpoint
GET /health/ready
Purpose: tells Kubernetes whether the pod can accept traffic. If this fails, the pod is removed from the load balancer (but not restarted). Check all dependencies the service needs to serve requests.
// Go example
func readinessHandler(w http.ResponseWriter, r *http.Request) {
checks := map[string]CheckResult{}
overall := "ok"
// Database check
ctx, cancel := context.WithTimeout(r.Context(), 2*time.Second)
defer cancel()
if err := db.PingContext(ctx); err != nil {
checks["db"] = CheckResult{Status: "fail", Error: err.Error()}
overall = "fail"
} else {
start := time.Now()
db.PingContext(ctx)
checks["db"] = CheckResult{Status: "ok", LatencyMs: time.Since(start).Milliseconds()}
}
// Redis check
if err := cache.Ping(r.Context()).Err(); err != nil {
checks["cache"] = CheckResult{Status: "fail", Error: err.Error()}
overall = "fail"
} else {
checks["cache"] = CheckResult{Status: "ok"}
}
status := http.StatusOK
if overall == "fail" {
status = http.StatusServiceUnavailable
}
w.Header().Set("Content-Type", "application/json")
w.WriteHeader(status)
json.NewEncoder(w).Encode(HealthResponse{Status: overall, Checks: checks})
}
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 · 168 lines · 58 tokens per session scan A 9a8ed547ee67
health-check-endpoints is a skill published in the GitHub repository soulcodex/agentic (10 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 1,192 once invoked, about $0.0002 per session on Opus 5.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
hatch3r-scalability-verify
Scalability verification gate before commit/release — stateless-handler ratio, back-pressure patterns, idempotency-key adoption, queue-based offloading, pool sizing, bulkheads, load-test pass at target scale.
mirrord-temporal
Helps DevOps engineers configure mirrord Operator's Temporal task queue splitting feature end-to-end. Generates the MirrordSplitConfig and MirrordPropertyList Kubernetes CRD YAMLs, the matching mirrord.json splitqueues section with messagefilter and jqfilter, and Helm value guidance. Use this skill whenever the user…
wikipedia
Search and read Wikipedia via x wkp — MediaWiki API, no API key, zero install; query, extract, suggest, and DDG route in one module. Load for wiki, wikipedia, encyclopedia lookup, article summary.
api-less-website
api-less-website skill — placeholder, documentation to be added. Do not load as a real skill yet.
04-security
A security and operations guide for deploying Dify, an open-source platform for building AI applications, in production.
java-actions
Create and call custom Java actions — extending Mendix with server-side Java, and invoking those actions from microflows in MDL. Use when logic needs a Java library, an algorithm microflows cannot express, or an integration only available in Java.