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 agentmods add skills/robinslange/learning-loop/healthnpx skills add robinslange/learning-loop --skill healthgit clone --depth 1 https://github.com/robinslange/learning-loopWrote 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/robinslange/learning-loop/health)<a href="https://agentmods.dev/skills/robinslange/learning-loop/health"><img src="https://agentmods.dev/badge/skills/robinslange/learning-loop/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 | $0.00081 | $0.03941 |
| Opus 5 | $0.00041 | $0.01971 |
| Sonnet 5 | $0.00016 | $0.00788 |
| Haiku 4.5 | $0.00008 | $0.00394 |
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 today.
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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Health: Vault Health Dashboard
Overview
Quick-check command that surfaces vault hygiene issues: ghost duplicates, near-duplicate pairs, orphan notes, stale inbox entries, embedding gaps, and broken wikilinks. Fast by default, deep on demand, with optional auto-fix for safe operations.
When to Use
/healthor/health --light: quick vault status check (default)/health --deep: full diagnostic with note-scorer analysis/health --auto: auto-fix safe issues (combinable with either mode)- After a burst of
/reflectsessions - Before
/inboxto see what needs attention - Periodic maintenance
Argument Parsing
| Input | Mode | Auto-fix |
|---|---|---|
/health |
light | no |
/health --light |
light | no |
/health --deep |
deep | no |
/health --auto |
light | yes |
/health --deep --auto |
deep | yes |
/health --provenance |
provenance | no |
/health --librarian |
librarian | no |
Process
Step 0: Parameter Resolution
No arguments (/health):
Run light mode immediately (fast, no prompting needed: it's the default and completes in seconds). Teach the other modes through results, not upfront prompting.
But after presenting results, if issues were found, mention available modes:
Found N issues. Options:
/health --deep: full analysis with note scoring/health --auto: auto-fix safe issues (ghost dupes, broken links)/health --provenance: pipeline observability (fabrication rates, agent stats)/health --deep --auto: both
This teaches the modes through use rather than upfront prompting.
Step 0.5: Mode Dispatch (--provenance / --librarian)
If one of these flags is present, skip all vault health checks and execute the matching mode file, then stop (do not proceed to Step 1):
- --provenance: read
${CLAUDE_PLUGIN_ROOT}/skills/health/modes/provenance.mdand execute it. - --librarian: read
${CLAUDE_PLUGIN_ROOT}/skills/health/modes/librarian.mdand execute it.
What ships with it
2 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.
- today Changed 75dbd6a8f8d3
- 4d ago First seen · 298 lines · 81 tokens per session scan A ad3d06af54a3
health is a skill published in the GitHub repository robinslange/learning-loop (12 stars, last pushed today), licensed Apache-2.0. It adds 81 tokens to every session and 3,941 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…