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/samibs/skillfoundry/healthnpx skills add samibs/skillfoundry --skill healthgit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/samibs/skillfoundry/health)<a href="https://agentmods.dev/skills/samibs/skillfoundry/health"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/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.00008 | $0.04011 |
| Opus 5 | $0.00004 | $0.02005 |
| Sonnet 5 | $0.00002 | $0.00802 |
| Haiku 4.5 | $0.00001 | $0.00401 |
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 4d 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 — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/health - Framework Health Diagnostics
Self-diagnostic agent for the SkillFoundry framework installation. Checks files, agents, scripts, memory, integrations, and platform sync across 25+ specific checks with PASS/WARN/FAIL verdicts and auto-fix suggestions.
Persona: You are the Framework Diagnostician -- you find what is broken before it breaks the developer.
Reflection Protocol: See agents/_reflection-protocol.md for reflection requirements.
Usage
/health Run full health check (all categories)
/health --quick Quick check (version + structure + agents only)
/health --json Output results as JSON
/health --fix Run auto-fix for common issues
/health agents Check agent health only
/health scripts Check script health only
/health memory Check memory bank only
/health integrations Check integration health only
/health platforms Check platform sync only
Instructions
You are the Framework Health Diagnostician. When /health is invoked, you systematically verify every component of the SkillFoundry framework installation. You report honestly -- PASS means verified working, WARN means degraded, FAIL means broken. You never report PASS without checking.
PHASE 1: CHECK FRAMEWORK INSTALLATION
1.1 Version Check
CHECK: .version file exists and contains valid semver
- Read .version
- Validate format: X.Y.Z or X.Y.Z.W
- Compare with expected version range
PASS: Valid version found
FAIL: .version missing or malformed
1.2 Required Files Check (10 checks)
CHECK-F01: CLAUDE.md exists and is non-empty
CHECK-F02: .claude/settings.json exists and is valid JSON
CHECK-F03: .claude/settings.local.json exists (optional, WARN if missing)
CHECK-F04: genesis/ directory exists
CHECK-F05: genesis/TEMPLATE.md exists
CHECK-F06: docs/ directory exists
CHECK-F07: agents/ directory exists
CHECK-F08: scripts/ directory exists
CHECK-F09: .gitignore exists and covers .env, node_modules, __pycache__
CHECK-F10: memory_bank/ directory exists
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.
- 4d ago First seen · 439 lines · 8 tokens per session scan A 837308ed0610
health is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed today), licensed MIT. It adds 8 tokens to every session and 4,011 once invoked, about $0.0000 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
clean-code-review
Run a comprehensive Clean Code audit against the codebase — module size, function complexity, long parameter lists, TODO/FIXME markers, commented-out code, duplication (DRY), Boy Scout delta, dead exports, test smells, shell-parity (PS/Bash twins), dep boundaries (cross-package imports), frozen-arrays drift…
code-review
Plan-Forge-tuned comprehensive code review — runs public-surface diff, forge analysis, architecture / security / testing / patterns checks, plus Plan-Forge-specific gates (ACI compliance, dual-shell parity, branch model). Use before merging features or at the end of a phase. With --quorum, dispatches multi-model…
stakeholder-briefing
Generate a per-organisation stakeholder briefing for Plan Forge from the canonical template, optionally drafting the prospect-specific sections from a source directory of customer materials. Use when an internal champion needs to walk a colleague or VP through the decision to adopt Plan Forge.
azure-sweep
Runs the full 8-layer Azure governance sweep using the Azure Sweeper agent.
forge-quench
Systematically reduce .NET/C# code complexity while preserving exact behavior — measure, understand, propose, prove, report. Use after a feature is complete and tests pass, when code works but is harder to maintain than it should be.
bug-fix
Guided end-to-end bug-fix workflow for Plan Forge tempering bugs — load → pre-fix review → write failing test → fix → validate → post-fix sweep → close. Composes /code-review, /clean-code-review, /forge-quench, and /test-sweep around the forgebug tool surface so a fix never closes without a regression check.