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 CodeInfinity1/Stram --skill system-health-checkgit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/system-health-check)<a href="https://agentmods.dev/skills/codeinfinity1/stram/system-health-check"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/system-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/skills/codeinfinity1/stram/system-health-check"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/system-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.00029 | $0.00559 |
| Opus 5.5 | $0.00012 | $0.00224 |
| Sonnet 5.5 | $0.00006 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
system-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 1mo 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System Health Check
Purpose
Give the assistant a reliable view of local readiness before running complex tasks. This skill checks environment and integration health without pretending missing providers are working.
When To Use
Use before end-to-end smoke tests, local model/voice/channel/browser setup, app troubleshooting, dependency diagnosis, or when the user asks whether the system is ready.
Inputs And Evidence
- User's target workflow and required capabilities.
- System status, provider status, channel doctor output, external integration status, and browser readiness.
- Missing environment variables, binaries, models, or local services.
Tool Map
system_statusexternal_integrations_statusvoice_provider_statusbrowser_live_statuschannel_doctoractivity_policytool_searchcapability_surfaceagent_skill_script_catalogagent_skill_script_run
Native Scripts
scripts/check_readiness.py: collects workspace, data directory, Python runtime, skill count, and redacted environment-presence facts. Use throughagent_skill_script_runwhen a compact local readiness snapshot is useful.
Workflow
- Identify the workflow being checked: voice, browser, OS control, channels, local models, or full agent.
- Query the relevant native status tools.
- Separate working, missing, disabled, unconfigured, and unsupported capabilities.
- Recommend the smallest native setup step for each blocker.
- Do not install or run external code unless the user approves the exact action.
- Re-run targeted checks after fixes.
Native Implementation Boundaries
- Use Stram status and capability tools.
- Do not call upstream health-check scripts from external reference/external reference/Windows-use.
- Do not infer readiness from installed reference repos alone.
Safety And Approval
- Status checks should not expose secrets; report presence/missing rather than raw values.
- Environment changes, installs, and service starts require approval where applicable.
- Avoid broad scans of private locations unless required.
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.
- 1mo ago First seen · 76 lines · 29 tokens per session scan A 852a04896578
system-health-check is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 559 once invoked, about $0.0001 per session on Opus 5.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
omh-live-incident-response
This is an OMH live-incident-response workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
debugging
Use this skill when something is broken and the cause is unknown — a failing test, a crash, an error message, wrong output, a regression, a hang, or behaviour that differs between environments — and it has to be found and fixed at the root. Also use it to build the failing proof for a suspected defect before fixing…
thinking-five-whys-plus
When a fault is localized and the proximate cause is known but the systemic root is not, chain evidence-linked whys with a counterfactual stop and a countermeasure.
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
postmortem
Deliver a structured post-mortem after incidents, mistakes, or stuck sessions. Use when the user requests a structured post-mortem after incidents, mistakes, or stuck sessions.
debug
Structured platform troubleshooting — classifies the problem layer, collects evidence, forms a root-cause hypothesis, and proposes a fix with validation and rollback steps.