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 OKHP3/skillz --skill publish-health-checkgit clone --depth 1 https://github.com/OKHP3/skillzWrote 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/okhp3/skillz/publish-health-check)<a href="https://agentmods.dev/skills/okhp3/skillz/publish-health-check"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/publish-health-check/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/okhp3/skillz/publish-health-check"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/publish-health-check.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.00035 | $0.01167 |
| Opus 5 | $0.00017 | $0.00583 |
| Sonnet 5 | $0.00007 | $0.00233 |
| Haiku 4.5 | $0.00003 | $0.00117 |
Grade A, and why
publish-health-check 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish health check
Notices, without anyone manually querying the Actions API, when a Skillz Forge publish silently stops going live.
Why this exists
.github/workflows/deploy-pages.yml once failed on every push for months
after a monorepo migration, and nobody noticed: pushes to main looked
normal, but the live site quietly served a stale build. There was no signal
that surfaced the failure without an agent deliberately going and checking.
This check closes that gap two ways at once:
- It re-checks the last
deploy-pages.ymlrun's conclusion formain, so a failed publish is flagged even if nobody is watching the Actions tab. - It independently compares the live
catalog.json'ssourceCommitagainst the commit that the last successful deploy run actually built (itshead_sha) -- not againstmain's current tip, sincedeploy-pages.ymlonly fires on apush.pathsallowlist and plenty of legitimatemaincommits (docs, unrelated workflows) never trigger a deploy at all. A mismatch here means a run reported "success" but didn't actually ship the commit it built (a stale Pages cache, a mis-scoped artifact, etc.) -- reporting success is not the same as being live.
Running it
node .agents/skills/publish-health-check/run.mjs
node .agents/skills/publish-health-check/run.mjs --json validation-reports/publish-health-check.json
No credentials are required -- it only issues public, unauthenticated
fetch calls against the GitHub REST API (workflow run history) and the
published GitHub Pages site.
Regression check: a main commit that does not touch any of
deploy-pages.yml's watched paths never triggers a deploy, so it must not
be misreported as a stale site. This was verified by pushing a change to the
top-level README (which matches none of deploy-pages.yml's push.paths
patterns -- unlike this SKILL.md, which does) and confirming the check still
reported healthy, correctly comparing against the previous successful
run's head_sha instead of main's new tip.
What ships with it
5 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.
- 11d ago First seen · 108 lines · 35 tokens per session scan A e750625fadad
publish-health-check is a skill published in the GitHub repository OKHP3/skillz (3 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 1,167 once invoked, about $0.0002 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
github-actions
Use this skill when authoring or debugging GitHub Actions workflows (.github/workflows/.yml) — e.g. "add CI for this Drupal project on GitHub", "run phpcs/phpstan/phpunit on pull requests", "cache composer dependencies", "deploy over SSH when main is pushed", "why didn't my workflow trigger", or anything involving…
gitlab-ci
Use this skill when authoring or debugging GitLab CI/CD pipelines (.gitlab-ci.yml) — e.g. "add a CI pipeline for this Drupal project", "run phpcs/phpstan/phpunit in GitLab CI", "deploy with drush from a pipeline", "why is my job not running", "cache composer dependencies", or anything involving stages, rules…
trusted-publish
Publish a package from a git repo to its registry via OIDC Trusted Publishing — no long-lived tokens. Writes the GitHub Actions publish workflow, walks the user through the registry-side trust entry, releases, and verifies. Use when the user wants to publish or release a package to PyPI, npm, crates.io, or another…
vastai
Vast.ai CLI to manage GPU instances, volumes, serverless endpoints, and billing.
vastai-sdk
Vast.ai Python SDK — high-level API for GPU instances, volumes, serverless endpoints, and billing.
pm-portfolio
A product-portfolio planning workflow for comparing several products and deciding where each fits in its market and lifecycle.