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-updategit 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-update)<a href="https://agentmods.dev/skills/eliyce/paqad-ai/module-health-update"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/module-health-update/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-update"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/module-health-update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, 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 Prompt Injection · line 22 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Agent Snooping · line 89 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.
- medium Agent Snooping · line 92 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.00149 | $0.01478 |
| Opus 5 | $0.00075 | $0.00739 |
| Sonnet 5 | $0.00030 | $0.00296 |
| Haiku 4.5 | $0.00015 | $0.00148 |
Grade A, and why
module-health-update 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What It Does
Refreshes the health of every module in the project in a single pass, combining the two complementary update paths so a profile is never left frozen at its onboarding stub:
| Pass | Source | Fields it updates |
|---|---|---|
| rollup | The active stack pack's declared coverage + test reports, attributed to modules via module-map.yml sources: globs. |
coverage_pct, tests_passing, tests_failing, tests_total, change_velocity |
| sync | Pending session evidence + the changed-files list + verification status. | defect_frequency, contract_stability, verification status, tier |
Order matters: rollup first (report context), sync second (diff + verification context). The two write to different fields of the same .paqad/module-health/<slug>.json record and never conflict.
This is the on-demand counterpart to the automatic refresh that the verification backstop performs on every completion. Run it when you want to recompute everything at once.
Use This When
- A user prompt matches the priority-225 router rules (
update module health,refresh module health,update all module health,update modules health,check module health,recompute module health). - You have just landed a batch of changes and want every touched module's tier brought current before reporting.
- A module's profile still reads
tier: unknownwith all metricsnull(the onboarding stub) and you want to populate it.
Inputs
- The active stack pack's
module_healthblock — declaressource_rootsplus the coverage / test report formats and paths. When absent, the rollup pass recordsblocked: module_health_unknownand is skipped; the sync pass still runs. module-map.yml(read-only) for slug attribution.- Pending evidence under
.paqad/module-health-evidence/and the changed-files list, consumed by the sync pass.
What ships with it
8 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.
- agents/openai.yaml 347 B
- assets/templates/update-summary.md 912 B
- references/update-vs-rollup.md 2.4 KB
- scripts/is-blocked.sh 1.2 KB runs code
- scripts/list-blocked-metrics.sh 1.4 KB runs code
- scripts/list-unattributed.sh 1.1 KB runs code
- scripts/list-updated.sh 1.1 KB runs code
- scripts/refresh.sh 1.5 KB runs code
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 · 93 lines · 149 tokens per session scan A 625c2dcf5846
module-health-update is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed today), licensed MIT. It adds 149 tokens to every session and 1,478 once invoked, about $0.0007 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.