helthcheck

A ready-made health-check endpoint for an Elixir app. The `/health` URL reports whether the app and services such as its database, Redis, and downstream systems are working.

In plain words
What is it for?
Use it to install and configure `/health`, choose the checks it runs, and add custom checks for app dependencies.
Why use it?
It gives a load balancer or uptime monitor one URL to check, so unhealthy app instances can be avoided and service problems detected.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/fullstack-phoenix/saas_kit/helthcheck
Any agent
npx skills add fullstack-phoenix/saas_kit --skill helthcheck
Clone the repo
git clone --depth 1 https://github.com/fullstack-phoenix/saas_kit

Made for: Claude Code, Codex.

Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 730 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00040 $0.00730
Opus 5 $0.00020 $0.00365
Sonnet 5 $0.00008 $0.00146
Haiku 4.5 $0.00004 $0.00073

Measured yesterday against content hash 53a91d9c6091, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

helthcheck 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 yesterday.

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/helthcheck/SKILL.md · 85 lines

How it starts

The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Health Check Endpoint

Adds a /health endpoint via plug_checkup. It returns HTTP 200 when the app and its dependencies (DB, Redis, downstream services) are healthy, and a non-200 when they are not — so a load balancer or uptime monitor can route around an unhealthy instance.

When to use

  • The app is deployed behind a load balancer or platform (Fly, Render, AWS, Kubernetes) that needs a health probe URL.
  • You want an uptime monitor (BetterStack, Pingdom, UptimeRobot) to confirm the app and its dependencies are reachable.
  • Don't reach for this if you only need a bare liveness ping with no dependency checks — a one-line Plug returning 200 is simpler.

Dependencies

  • Requires: None.
  • Recommended: None.

Install

mix saaskit.feature.install helthcheck

Adds the plug_checkup package and wires the /health route. No install decisions to answer.

What it generates

  • Adds plug_checkup to mix.exs deps.
  • A health check plug/route mounted at /health in lib/my_app_web/router.ex.
  • A checkup definition module that lists the checks run on each request (DB connectivity by default).

Configuration

plug_checkup is configured through the checks list passed to the plug rather than config/*.exs. The default check verifies the repo is reachable.

Tweaking for your app

Add a custom checkup for a downstream dependency. Define a check module:

# lib/my_app/health/redis_check.ex
defmodule MyApp.Health.RedisCheck do
  def call do
    case MyApp.Redis.ping() do
      :ok -> :ok
      error -> {:error, error}
    end
  end
end

Register it alongside the default DB check where the health plug is mounted:

# lib/my_app_web/router.ex
forward "/health", PlugCheckup,
  PlugCheckup.Options.new(
    json_encoder: Jason,
    checks: [
      %PlugCheckup.Check{name: "DB", module: MyApp.Health.DBCheck, function: :call},
      %PlugCheckup.Check{name: "Redis", module: MyApp.Health.RedisCheck, function: :call}
    ]
  )

Read the full file on GitHub · 85 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. yesterday First seen · 85 lines · 40 tokens per session scan A 53a91d9c6091

Subscribe to this mod's changes

helthcheck is a skill published in the GitHub repository fullstack-phoenix/saas_kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 730 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens