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.
git clone --depth 1 https://github.com/boparaiamrit/skills-by-amritWrote 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/commands/boparaiamrit/skills-by-amrit/health-check)<a href="https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/health-check"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/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.
<a href="https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/health-check"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/health-check.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00037 | $0.01067 |
| Opus 5 | $0.00018 | $0.00534 |
| Sonnet 5 | $0.00007 | $0.00213 |
| Haiku 4.5 | $0.00004 | $0.00107 |
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 12d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/health-check — Product Completeness Audit
Audit the entire product for functional completeness. Find every placeholder page, broken flow, disconnected API, and missing state.
Prerequisites
- A running or buildable application
- Expectation of what "done" looks like
Instructions
Step 1: Determine Scope
From $ARGUMENTS:
routes→ Only audit route/page completenessflows→ Only audit user flow completenessapi→ Only audit API connection completenessfullorallor empty → Run the full audit (all three)
Step 2: Route Inventory
Extract every route and page:
# Find all page files
find . -type f \( -name "page.tsx" -o -name "page.jsx" \) -not -path "*/node_modules/*" -not -path "*/.next/*" 2>/dev/null
# Find pages directory
find . -type f -path "*/pages/*" \( -name "*.tsx" -o -name "*.jsx" \) -not -path "*/node_modules/*" -not -path "*/.next/*" 2>/dev/null
# Find router config
grep -rn "path:\|Route\|route" --include="*.ts" --include="*.tsx" . | grep -vi "node_modules\|.git\|dist" | head -30
Create Route Inventory: | # | Route | Component | Auth | Status (Level 0-5) |
Step 3: Placeholder Detection
# Hardcoded data
grep -rn "lorem\|ipsum\|placeholder\|fake\|dummy\|John Doe\|jane@\|test@example\|sample\|hardcoded\|TODO\|FIXME" --include="*.ts" --include="*.tsx" --include="*.js" --include="*.jsx" . | grep -vi "node_modules\|.git\|dist\|.next\|test\|spec\|__mock" | head -40
# Inline arrays (possible hardcoded data)
grep -rn "const.*=.*\[{" --include="*.ts" --include="*.tsx" --include="*.js" --include="*.jsx" . | grep -vi "node_modules\|.git\|dist\|.next\|test\|spec\|type\|interface" | head -30
Step 4: Page-by-Page Audit
For EACH route (no exceptions), determine:
- Completeness Level (0=Skeleton, 1=Wireframe, 2=Demo, 3=Connected, 4=Functional, 5=Complete)
- Data Source — Real API or hardcoded?
- Loading State — Exists?
- Error State — Exists?
- Empty State — Exists?
- Interactivity — All buttons/forms work?
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.
- 12d ago First seen · 122 lines · 37 tokens per session scan A 75f8d706ad36
health-check is a command published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 6mo ago), licensed MIT. It adds 37 tokens to every session and 1,067 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.
Other commands, from other repositories
checkpoint
Save verification state and progress checkpoint.
implement
Execute tasks from a track's implementation plan following TDD workflow.
shipwright-enhance
Add features to an existing Shipwright project.
verify-work
Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
workflow-implement
Exécuter la phase d'Implémentation - développement sprint avec TDD/BDD.
aqa-flow
Router workflow for test automation: routes to ui-aqa-flow, api-aqa-flow, or testgen-flow. Kept for backward compatibility.