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 OZmasterAI/Torus-Framework --skill super-healthgit clone --depth 1 https://github.com/OZmasterAI/Torus-FrameworkWrote 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/ozmasterai/torus-framework/super-health)<a href="https://agentmods.dev/skills/ozmasterai/torus-framework/super-health"><img src="https://agentmods.dev/badge/skills/ozmasterai/torus-framework/super-health.svg" alt="Measured on agentmods" 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.00000 | $0.01065 |
| Opus 5 | $0.00000 | $0.00532 |
| Sonnet 5 | $0.00000 | $0.00213 |
| Haiku 4.5 | $0.00000 | $0.00106 |
Grade A, and why
super-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 8d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/super-health — Comprehensive Framework Health Diagnostic
Merged from: /health + /health-report + /status
When to use
When the user says "super-health", "super health", "full health", "deep diagnostics", "comprehensive status", or wants the most thorough health check combining quick diagnostics, deep metrics, and operational overview in one skill.
Commands
/super-health— Full comprehensive diagnostic (all checks + deep metrics)/super-health --quick— Quick dashboard only (like /status — fast, pre-formatted)/super-health --repair— Run diagnostic and auto-fix common issues/super-health --brief— Summary-only version (no detailed metrics)/super-health --export— Save report to disk as markdown + JSON
Flow
1. QUICK DASHBOARD (always runs first)
Run the quick status gather:
python3 ~/.claude/skill-library/status/scripts/gather.py
Display the pre-formatted dashboard output to the user immediately.
If --quick flag is set, stop here.
2. DEEP DIAGNOSTICS
Run the health check script:
python3 ~/.claude/skill-library/super-health/scripts/check.py
If --repair flag is given:
python3 ~/.claude/skill-library/super-health/scripts/check.py --repair
This checks:
- Memory MCP: process running (pgrep) + ChromaDB accessible
- Gates: all gate files present + importable
- State: valid JSON, correct schema version
- Ramdisk: mounted, writable
- File claims: stale claims (>2 hours old)
- Audit logs: today's log exists, not oversized (>5MB)
- Deferred items: count from Gate 9 deferrals
- PRPs: any active PRPs with stuck tasks
3. COMPREHENSIVE METRICS
Gather deep metrics for the full report:
- Read
.gate_effectiveness.jsonfor gate block/override/prevent statistics - Check circuit_breaker state summary (ok/degraded/tripped + trip counts)
- Count and verify all gates are present and importable
- Query memory MCP for knowledge count
- Read
LIVE_STATE.jsonfor known_issues, test counts, framework_version - Read
stats-cache.jsonfor test results - Check git branch + recent commits:
git -C ~/.claude log --oneline -5 git -C ~/.claude branch --show-current
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 124 lines · 0 tokens per session scan A eec7825d7d27
super-health is a skill published in the GitHub repository OZmasterAI/Torus-Framework (5 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,065 tokens. 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.