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 joozio/agent-wellbeing-kit --skill agent-health-checkgit clone --depth 1 https://github.com/joozio/agent-wellbeing-kitWrote 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/joozio/agent-wellbeing-kit/agent-health-check)<a href="https://agentmods.dev/skills/joozio/agent-wellbeing-kit/agent-health-check"><img src="https://agentmods.dev/badge/skills/joozio/agent-wellbeing-kit/agent-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/joozio/agent-wellbeing-kit/agent-health-check"><img src="https://agentmods.dev/badge/skills/joozio/agent-wellbeing-kit/agent-health-check.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.00045 | $0.00515 |
| Opus 5 | $0.00023 | $0.00258 |
| Sonnet 5 | $0.00009 | $0.00103 |
| Haiku 4.5 | $0.00005 | $0.00052 |
Grade A, and why
agent-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 11d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Health Check
Agents fail silently: they retry the same broken call for hours, or their memory files bloat and go stale until output quality drops. This skill catches both. Run the tools from the kit directory (adjust the path to where agent-wellbeing-kit is installed).
Error scan
Scan the agent's log for repeating errors and stuck loops:
python3 /path/to/agent-wellbeing-kit/error_registry.py --scan /path/to/agent.log
Or pipe recent output directly:
tail -n 500 agent.log | python3 error_registry.py --feed
Exit 1 means alerts fired. How to read the output:
- Repeating: the same error fingerprint 3+ times. Something is broken and being retried. Find the root cause; do not just note it.
- Possible stuck loops: one fingerprint 5+ times. The agent is likely wedged on a single operation. Check whether that process should be restarted or that task abandoned.
- High error volume: more than 50 errors in the scanned window. Widen the investigation beyond single fingerprints.
Timestamps, UUIDs, hex IDs, and numbers are stripped before fingerprinting, so the counts group true repeats even when metadata differs.
Memory health
python3 memory_health.py --check /path/to/memory/
- bloat: file over the size threshold. Compact it: summarize, archive old entries, split by topic.
- stale: not modified past the threshold. Either the memory system stopped writing (a bug worth chasing) or the file is dead weight (archive it).
- not found: a configured path is missing. The memory system may be writing somewhere else; find where.
Reporting
Summarize findings at a high level: what is broken, since when, and the one action that fixes it. If everything is clean, say so in one line. Persisted results land in state.json and show up in dashboard.html.
If a finding needs the human's attention right now, check quiet hours first (see the wellbeing-boundaries skill). Most health findings belong in the next scheduled report, not a midnight ping.
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.
- 11d ago First seen · 47 lines · 45 tokens per session scan A 80c7b4961ff5
agent-health-check is a skill published in the GitHub repository joozio/agent-wellbeing-kit (10 stars, last pushed 13d ago), licensed MIT. It adds 45 tokens to every session and 515 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 skills, from other repositories
mem0-status
Diagnoses mem0 connectivity, API key validity, and memory read/write functionality. Use when memory operations fail, searches return empty, addmemory errors occur, or to verify the plugin is working correctly.
inspector-workbench
Runs Inspector UI work on the standalone Threads state lab so the agent can see the overlay. Use when a CopilotKit employee asks an agent to fix, polish, add, or debug Inspector UI, chrome, panes, overlay actions, launcher, Home, Threads, Playground, Memory, or any visual behavior in @copilotkit/web-inspector. Don't…
md-audit
Read-only code quality audit — scan the current working directory for common issues (bugs, dead code, security hotspots, missing error handling) and return a prioritised findings report. No files are edited. Use when asked to "audit the code", "quick audit", "find issues", "code scan", or "what's wrong with this…
potpie-debug-memory
Use while debugging or troubleshooting failures, flaky tests, incidents, production alerts, CI failures, local dev setup issues, repeated bugs, prior fixes, failed attempts, and verification history.
browserwing-admin
Manage and operate BrowserWing — an intelligent browser automation platform. Install dependencies, configure LLM, create/manage/execute automation scripts, use AI-driven exploration to generate scripts, browse the script marketplace, and troubleshoot issues.
exploiting-linux-kernel-vulnerabilities
Methodology for discovering and exploiting Linux kernel memory-corruption vulnerabilities (UAF, OOB read/write, race/TOCTOU, type confusion) during authorized engagements, covering reachability analysis, building stable read/write primitives from a single bug, defeating KASLR/SMEP/SMAP/KPTI, slab/buddy heap grooming…