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 HECer/yoke --skill healthgit clone --depth 1 https://github.com/HECer/yokeWrote 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/hecer/yoke/health)<a href="https://agentmods.dev/skills/hecer/yoke/health"><img src="https://agentmods.dev/badge/skills/hecer/yoke/health/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/hecer/yoke/health"><img src="https://agentmods.dev/badge/skills/hecer/yoke/health.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.00059 | $0.01715 |
| Opus 5 | $0.00030 | $0.00857 |
| Sonnet 5 | $0.00012 | $0.00343 |
| Haiku 4.5 | $0.00006 | $0.00171 |
Grade A, and why
health 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 9d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Quality Dashboard
You are running the health skill. Detect and run the project's quality tools, score each category, and present a dashboard.
Step 1: Detect the health stack
Read CLAUDE.md and look for a ## Health Stack section that lists the project's tools. If found, use those tools. If not found, auto-detect:
# Runtime detection
[ -f Gemfile ] && echo "RUNTIME:ruby"
[ -f package.json ] && echo "RUNTIME:node"
[ -f requirements.txt ] || [ -f pyproject.toml ] && echo "RUNTIME:python"
[ -f go.mod ] && echo "RUNTIME:go"
[ -f Cargo.toml ] && echo "RUNTIME:rust"
# Type checker
[ -f tsconfig.json ] && echo "TYPECHECK:tsc"
[ -f pyproject.toml ] && command -v mypy >/dev/null 2>&1 && echo "TYPECHECK:mypy"
[ -f Gemfile ] && grep -q "sorbet" Gemfile 2>/dev/null && echo "TYPECHECK:sorbet"
# Linter
[ -f .eslintrc* ] || [ -f eslint.config* ] && echo "LINT:eslint"
[ -f .rubocop.yml ] && echo "LINT:rubocop"
[ -f pyproject.toml ] && grep -qE "ruff|flake8" pyproject.toml 2>/dev/null && echo "LINT:ruff"
[ -f go.mod ] && echo "LINT:staticcheck"
[ -f Cargo.toml ] && echo "LINT:clippy"
# Test runner
[ -f jest.config* ] || [ -f vitest.config* ] && echo "TESTS:npm run test"
[ -f .rspec ] && echo "TESTS:bundle exec rspec"
[ -f pytest.ini ] || [ -f conftest.py ] && echo "TESTS:pytest"
[ -f go.mod ] && echo "TESTS:go test ./..."
[ -f Cargo.toml ] && echo "TESTS:cargo test"
# Dead code detector
command -v ts-prune >/dev/null 2>&1 && echo "DEADCODE:ts-prune"
command -v knip >/dev/null 2>&1 && echo "DEADCODE:knip"
[ -f go.mod ] && echo "DEADCODE:deadcode (go-deadcode)"
[ -f Cargo.toml ] && echo "DEADCODE:cargo udeps"
Print the detected stack. If nothing is detected, ask the user what tools to run.
Step 2: Run the tools
Run each detected tool and capture output. Run them in parallel where possible.
Type checker (run the project's own type-checker, e.g. tsc --noEmit, mypy ., srb tc):
# Example for TypeScript:
npx tsc --noEmit 2>&1 | tail -20
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.
- 9d ago First seen · 178 lines · 59 tokens per session scan A 168dc90d6b03
health is a skill published in the GitHub repository HECer/yoke (2 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 1,715 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.
Other skills, from other repositories
fix-bug
Diagnoses and fixes bugs using a test-first workflow (reproduce, diagnose, fix). Use this skill whenever the user reports a bug, describes unexpected behavior, or asks to investigate or fix a defect. Even if the user says "something's broken", "this isn't working", "fix this bug", or "why does X happen", load this…
ox-cli-doctor
Run diagnostic checks on SageOx configuration and integrations.
doctor
Diagnose Cladding runtime health — Claude Code hook liveness and version, CI package pinning, lifecycle governance, and sentinel-miss frequency by phase × cause × fallback. Use when hooks may be silent, CI may float across Cladding releases, scan or run results look thinner than expected, or before tuning the host…
debug
Debug issues with iterative fix loop. Gathers problem description, investigates, then enters fix-verify cycle. Triggers on "debug", "fix this", "troubleshoot". Use when the goal is to fix a specific reported issue. For exploration or new features, use brainstorm or plan-creation.
resolve-diagnostics
Resolves IDE diagnostics (inspections and analyzer findings) at the warning or higher severity level for a given set of files, then applies the solution's code style. Use this skill when a workflow's refactoring step calls for resolving diagnostics, or when the user asks to fix warnings, inspections, or static…
observability
Log and metrics analyst — reads .cladding/audit.log.jsonl, perf/baseline.json, and drift reports; surfaces patterns the human can act on. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized projects.