health-check-endpoints

health-check-endpoints is a skill for Claude Code, Codex from soulcodex/agentic. It costs 58 tokens per session (1,192 once invoked), scanned A, original, MIT.

A guide for adding liveness and readiness endpoints, which tell Kubernetes whether a service is running and ready to receive traffic.

In plain words
What is it for?
Use it to implement /health/live and /health/ready endpoints, dependency checks, probe settings, and circuit-breaker integration.
Why use it?
It helps Kubernetes restart broken processes and temporarily stop sending traffic to services whose dependencies are unavailable.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Codex; mentions OpenCode.

Good fit Use it to implement /health/live and /health/ready endpoints, dependency checks, probe settings, and circuit-breaker integration.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/soulcodex/agentic/health-check-endpoints
Install

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.

Any agent
npx skills add soulcodex/agentic --skill health-check-endpoints
Clone the repo
git clone --depth 1 https://github.com/soulcodex/agentic

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for health-check-endpoints

README.md
[![agentmods](https://agentmods.dev/badge/skills/soulcodex/agentic/health-check-endpoints/github.svg)](https://agentmods.dev/skills/soulcodex/agentic/health-check-endpoints)
Your own site
<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.

agentmods 80×15 button for health-check-endpoints

Your own site · 80×15
<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>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,192 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00058 $0.01192
Opus 5 $0.00029 $0.00596
Sonnet 5 $0.00012 $0.00238
Haiku 4.5 $0.00006 $0.00119

Measured 10d ago against content hash 9a8ed547ee67, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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 10d 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.

skills/backend/health-check-endpoints/SKILL.md · 168 lines

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 OK unless 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})
}

Read the full file on GitHub · 168 lines

Changes

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.

  1. 10d ago First seen · 168 lines · 58 tokens per session scan A 9a8ed547ee67

Subscribe to this mod's changes

health-check-endpoints is a skill published in the GitHub repository soulcodex/agentic (10 stars, last pushed 5d ago), licensed MIT. It adds 58 tokens to every session and 1,192 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-31.