What is health-check?

A codebase health-check tool that runs available tests, code-style checks, coverage checks, complexity checks, dependency audits, performance checks, and static analysis. It can compare results with an earlier report and save a new snapshot.

Use it to run all checks or selected checks, compare results from a chosen date, calculate a health grade, and store the results.

It brings several kinds of project quality checks into one review and helps reveal regressions, meaning the project has become worse since an earlier check.

health-check — Skill for Claude Code by fjpulidop

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 fjpulidop/specrails-core --skill health-check

Clone the repo

git clone --depth 1 https://github.com/fjpulidop/specrails-core

Made for: Claude Code.

Or install specrails, the plugin that ships this one along with the rest of its 28 skills, 14 agents.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/fjpulidop/specrails-core/health-check/github.svg)](https://agentmods.dev/skills/fjpulidop/specrails-core/health-check)

Your own site

<a href="https://agentmods.dev/skills/fjpulidop/specrails-core/health-check"><img src="https://agentmods.dev/badge/skills/fjpulidop/specrails-core/health-check/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/fjpulidop/specrails-core/health-check"><img src="https://agentmods.dev/badge/skills/fjpulidop/specrails-core/health-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 6,732 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.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00033	$0.06732
Opus 5	$0.00016	$0.03366
Sonnet 5	$0.00007	$0.01346
Haiku 4.5	$0.00003	$0.00673

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

Security

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

specrails-plugin/skills/health-check/SKILL.md · 531 lines

How it starts

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

Run a full health check for this project (read from CLAUDE.md or package.json): detect available tools, execute each quality check, compare results against the previous run, detect regressions, compute a health grade, and store a snapshot for future comparison.

Input: $ARGUMENTS — optional flags:

--since <date> — use the report from this date (ISO format: YYYY-MM-DD) as the comparison baseline instead of the most recent
--only <checks> — comma-separated subset to run. Valid values: tests, coverage, lint, complexity, deps, perf, static
--save — always save the snapshot even when --only is used (default: skip save for partial runs)

Phase 0: Argument Parsing

Parse $ARGUMENTS to set runtime variables.

Variables to set:

COMPARE_DATE — string (ISO date) or empty string. Default: "" (use most recent report).
CHECKS_FILTER — array of check names or the string "all". Default: "all".
SAVE_SNAPSHOT — boolean. Default: true when CHECKS_FILTER="all", false for partial runs unless --save is present.

Parsing rules:

Scan $ARGUMENTS for --since <date>. If found, set COMPARE_DATE=<date>. Strip from arguments.
Scan for --only <checks>. If found:
- Split <checks> on commas to produce an array.
- Validate each entry against the allowed set: tests, coverage, lint, complexity, deps, perf, static.
- If any unknown value is found: print Error: unknown check "<value>". Valid checks: tests, coverage, lint, complexity, deps, perf, static and stop.
- Set CHECKS_FILTER=<validated-array>.
- Set SAVE_SNAPSHOT=false (partial run — snapshot may be incomplete).
Scan for --save. If found, set SAVE_SNAPSHOT=true regardless of CHECKS_FILTER.

Print active configuration:

Running checks: <all | comma-separated list> | Static analysis: <enabled|disabled> | Comparing to: <COMPARE_DATE or "latest">

Phase 1: Toolchain Detection

Detect available tools for each check category. Run all detections simultaneously (in parallel). For each category, try tools in the order listed — use the first one found.

Read the full file on GitHub · 531 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.

11d ago First seen · 531 lines · 33 tokens per session scan A 83d5edddca43

Subscribe to this mod's changes

health-check is a skill published in the GitHub repository fjpulidop/specrails-core (9 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 6,732 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.

Claude Code Code Generation Debugging Testing ai-agents anthropic claude developer-tools

ward

Ward the codebase — an ad-hoc test-gap audit that reveals unguarded code (untested functions, uncovered edge cases, missing error-handling and integration tests) and conjures ready-to-paste test skeletons as protective wards against regression, surfaced inline in the session. Scoped to your current diff by default, or…

eric-cielo/moflo · 0 tokens

qa

QA Engineer for software quality. Use for bug reproduction, regression analysis, edge-case design, test strategy, writing or reviewing tests, verification plans, acceptance checks, and deciding whether implementation work actually satisfies the request.

Everyone-Needs-A-Copilot/claude-copilot · 44 tokens

ralphctl-debugging-and-error-recovery

Systematic root-cause debugging. Use when tests fail, builds break, or behaviour does not match expectations. Follow stop-the-line → reproduce → localize → reduce → root-cause → guard-with-regression-test → verify, not guessing; the reproduction and regression steps follow the same red-green discipline as…

lukas-grigis/ralphctl · 78 tokens

health-check