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 Eliyce/paqad-ai --skill module-health-rollupgit clone --depth 1 https://github.com/Eliyce/paqad-aiWrote 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/eliyce/paqad-ai/module-health-rollup)<a href="https://agentmods.dev/skills/eliyce/paqad-ai/module-health-rollup"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/module-health-rollup/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/eliyce/paqad-ai/module-health-rollup"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/module-health-rollup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 105 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00013 | $0.01626 |
| Opus 5 | $0.00006 | $0.00813 |
| Sonnet 5 | $0.00003 | $0.00325 |
| Haiku 4.5 | $0.00001 | $0.00163 |
Grade A, and why
module-health-rollup 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 12d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What It Does
Runs the test-driven module-health rollup defined by issue #80, Phase 3. For every module declared in module-map.yml, the rollup computes:
| Metric | Source |
|---|---|
coverage_pct |
Coverage report parsed via the pack's coverage_format parser. |
tests_passing |
Test report parsed via the pack's test_report_format parser. |
tests_failing |
Same. |
tests_total |
Same. |
change_velocity |
git log -- <sources> over git_window_days (default 14). |
contract_stability |
public_api_extractor output. Blocked when extractor absent. |
Coverage and test rows are attributed to module slugs by matching each file against module-map.yml's sources: globs. Files that match no module land in the report's unattributed_files list (surfaced to the user as a MM-ADD candidate for the reconciler).
Hard rule: no metric is fabricated or zeroed. When a signal cannot be computed the metric is set to null and the reason recorded in blocked_metrics (e.g. coverage:not_configured, tests:report_missing:<path>, contract_stability:no_public_api_extractor).
Use This When
feature-development.checksfinishes format/test/build and needs to refresh module health.paqad-ai module-health sync --from-report <path>is invoked.- The provider hook at
runtime/hooks/module-health-sync.shfires. - A user prompt asks to "refresh module health" or "roll up coverage".
Inputs
- The active stack pack's
module_healthblock — seeruntime/base/skills/module-health-rollup/references/coverage-formats.mdfor the closed format set. Required:source_roots, plus at least one of(coverage_format + coverage_path)or(test_report_format + test_report_path). module-map.yml(read-only) for slug attribution.- Optional
--from-report <path>to bypass the pack's report path (typical in CI).
What ships with it
7 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.
- 12d ago First seen · 107 lines · 13 tokens per session scan A 7177ea5a5df7
module-health-rollup is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 1,626 once invoked, about $0.0001 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
auto-qa
QAMESH project QA mesh — plan, run, report, and publish deterministic QA evidence.
auto-canary
A deployment health-check skill for testing whether a recently deployed or staging website is working. It runs build, end-to-end, and browser checks, then reports a pass, warning, or failure.
tdd
A Test-Driven Development guide. TDD means writing a failing test first, adding the smallest implementation that passes it, and then improving the code while keeping the tests passing.
testing-strategy
A testing guide that explains how to combine unit, integration, contract, and end-to-end tests. End-to-end tests check complete user flows, while integration tests check components working together.
debugging
A structured method for finding and fixing software bugs. It starts by writing a test that reproduces the failure, then investigates its underlying cause before making a small fix.
database-verification
Shell-based database connectivity and integrity checks. Verifies that databases are reachable, schemas match expectations, and data integrity constraints hold.