Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/aget-framework/template-advisor-agetnpx agentmods add skills/aget-framework/template-advisor-aget/aget-check-healthWrote 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/aget-framework/template-advisor-aget/aget-check-health)<a href="https://agentmods.dev/skills/aget-framework/template-advisor-aget/aget-check-health"><img src="https://agentmods.dev/badge/skills/aget-framework/template-advisor-aget/aget-check-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/aget-framework/template-advisor-aget/aget-check-health"><img src="https://agentmods.dev/badge/skills/aget-framework/template-advisor-aget/aget-check-health.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.00026 | $0.00634 |
| Opus 5 | $0.00013 | $0.00317 |
| Sonnet 5 | $0.00005 | $0.00127 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
aget-check-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 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.
This is a copy
100% identical to aget-check-health — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aget-check-health
Run health inspection on an AGET agent. This skill performs sanity checks, validates structure, and reports agent health status.
Instructions
When this skill is invoked:
-
Run the housekeeping script:
python3 scripts/health_check.py -
The script checks:
.aget/directory structureversion.jsonvalidityidentity.jsonvalidity (if exists)governance/directory contents- 5D directory structure
- L-doc count and format
-
Report the health status:
- Healthy (exit 0): All checks passed
- Warnings (exit 1): Non-blocking issues found
- Errors (exit 2): Blocking issues require attention
Output Format
Present the health report:
Sanity Check: [HEALTHY/WARNINGS/ERRORS]
Checks:
- Structure: [PASS/WARN/FAIL]
- Version: [PASS/WARN/FAIL]
- Identity: [PASS/WARN/FAIL]
- Governance: [PASS/WARN/FAIL]
[If warnings/errors, list specific issues]
Recommendations:
- [Action items if any]
Options
--json: Machine-readable output--dir /path: Run on specific agent directory
Remediation: This skill is detect-only. For auto-fixes and drift remediation, use /aget-enhance-health (SKILL-049, governing spec CAP-SESSION-014). Canonical check → enhance pipeline per DESIGN_DIRECTION §Principle 9.
Error Handling
- Exit code 0: All checks passed
- Exit code 1: Warnings found (list them)
- Exit code 2: Errors found (list them, recommend fixes)
- Exit code 3: Script configuration error
Related
/aget-enhance-health— Pair sibling: remediates drift detected by this skill (SKILL-049, CAP-SESSION-014)- L532: Skills vs Learnings Distinction
- L656: Loading Dock anti-pattern (
--fixremoved v1.1.0 — was documented but never implemented) - L671: Classification Without Consequence (
--fixwas unrooted at spec level) - CAP-SESSION-002: Sanity Check Protocol (legacy reference — canonical is CAP-SESSION-008)
- CAP-SESSION-014: Health Remediation Protocol (governs enhance-health pair skill)
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 · 81 lines · 26 tokens per session scan A df4dfdb8711d
aget-check-health is a skill published in the GitHub repository aget-framework/template-advisor-aget (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 26 tokens to every session and 634 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to aget-check-health, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
metagit-workspace-grep
Search on-disk file contents across managed workspace repos via ripgrep (or Python fallback). Use when hunting code strings, configs, or Terraform/Docker patterns — not for manifest metadata.
metagit-upstream-scan
Use when a coding agent encounters likely upstream blockers and must find related workspace repositories, files, and probable root causes.
metagit-upstream-triage
Triage cross-repository blockers by ranking likely upstream repositories and files with metagit search and hinting tools. Use when local fixes appear incomplete.
mypy
Skill "mypy" from bobmatnyc/claude-mpm, covering mypy - static type checking for python, basic mypy, with common type stubs, for fastapi projects and for django projects.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
gitnexus-debugging
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug".