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 manusco/resonance --skill system-healthgit clone --depth 1 https://github.com/manusco/resonanceWrote 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/manusco/resonance/system-health)<a href="https://agentmods.dev/skills/manusco/resonance/system-health"><img src="https://agentmods.dev/badge/skills/manusco/resonance/system-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/manusco/resonance/system-health"><img src="https://agentmods.dev/badge/skills/manusco/resonance/system-health.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00069 | $0.01229 |
| Opus 5 | $0.00034 | $0.00615 |
| Sonnet 5 | $0.00014 | $0.00246 |
| Haiku 4.5 | $0.00007 | $0.00123 |
Grade A, and why
resonance-ops-system-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 10d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/resonance-ops-system-health: measure the pulse, diagnose the drift
Role: the Doctor and benchmark engine. Invoked as:
/system-health(to run a full health check). Input: Codebase State. Output: Health Score (0-100) + Qualitative Flags. Definition of Done: A final score is calculated using Test/Lint/Build weights. Qualitative flags for Auth Inconsistency, Env Fragility, Shallow Tests, and State Drift are explicitly marked.
You need to measure the system's pulse. A "Healthy" system has high confidence (tests pass), low entropy (clean lint), synced state (Map == Territory), consistent authorization, and environmental safety.
Prerequisites (fail fast)
- Project is initialized (has a
.resonance/directory).
Algorithm (Execution)
Copy this checklist and tick items as you go.
- Automated Vitals: Detect the project's toolchain first (see Toolchain Detection); do not assume npm. Run the project's own commands:
- Tests: the project's test command, with coverage if available. (Weight: 40%)
- Lint: the project's lint command. (Weight: 30%)
- Build: the project's build command. (Weight: 30%)
- Manual Vitals (The Qualitative Flags):
- Drift Check: Read
01_state.md. Does it matchgit log -10? (Flag:DRIFT_DETECTED) - Auth Model Consistency: Do routes, policies, and UI templates agree on access rules? Delegate to
resonance-ops-security. (Flag:AUTH_INCONSISTENT) - Environment Assumption Check: Are there hardcoded paths or missing fallbacks? Would the app survive deploying to a fresh environment? (Flag:
ENV_FRAGILE) - Test Depth Check: Do tests cover failure paths and unauthorized paths? Quick scan against the 8-Path Matrix. Delegate to
resonance-ops-qa. (Flag:TEST_SHALLOW) - Stale Tests Check: Do tests encode product decisions that have since changed? (Flag:
STALE_TESTS)
- Drift Check: Read
- Calculation:
Score = (Test% * 0.4) + (LintClean * 0.3) + (BuildPass * 0.3)- Compile the qualitative flags.
- Synthesis: Output the Health Report.
What ships with it
4 files 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.
- 10d ago First seen · 99 lines · 69 tokens per session scan A 6411be906674
resonance-ops-system-health is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed 6d ago), licensed MIT. It adds 69 tokens to every session and 1,229 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-30.
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.