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 KalarisLabs/Skill-Doctor --skill release-publishgit clone --depth 1 https://github.com/KalarisLabs/Skill-DoctorWrote 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/kalarislabs/skill-doctor/release-publish)<a href="https://agentmods.dev/skills/kalarislabs/skill-doctor/release-publish"><img src="https://agentmods.dev/badge/skills/kalarislabs/skill-doctor/release-publish/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/kalarislabs/skill-doctor/release-publish"><img src="https://agentmods.dev/badge/skills/kalarislabs/skill-doctor/release-publish.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.00045 | $0.00239 |
| Opus 5 | $0.00023 | $0.00120 |
| Sonnet 5 | $0.00009 | $0.00048 |
| Haiku 4.5 | $0.00005 | $0.00024 |
Grade A, and why
release-publish 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 yesterday.
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.
What it actually says
Release
Only from a v* tag on main after required checks are green.
./scripts/prepublish-check.sh --full- CHANGELOG for the version
- Single workspace version bump
- PR → required checks → merge
git tag vX.Y.Z && git push origin vX.Y.Zrelease.yml: musl/darwin/win, checksums, SBOM, Sigstore, GitHub Releasecargo publishorder: neutralize → rules → core → sandbox → mcp → skill-doctornpm publish --access public@kalarislabs/skill-doctor(installer only)- Homebrew tap follow-up
Never: publish from CI on a non-tag; npm without matching binary checksums; skip dry-run; publish if deny/gitleaks is red.
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.
- yesterday First seen · 21 lines · 45 tokens per session scan A b88172df034c
release-publish is a skill published in the GitHub repository KalarisLabs/Skill-Doctor (11 stars, last pushed today), licensed Apache-2.0. It adds 45 tokens to every session and 239 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-09-11.
Other skills, from other repositories
release-readiness-check
Verify all prerequisites are met before a release by checking PRs, CI/CD status, environment health, and blocking issues across GitHub, ArgoCD, and Jira. Use before cutting a release, deploying to production, or during release planning.
swarm-release
Full SwarmAI release cycle: preflight checks, version bump, binary build, desktop package, smoke test, and GitHub publish. The single release path — handles version bump + tag plus build/package/smoke stages. TRIGGER: "release", "cut release", "ship it", "发版". NOT FOR: sswarm-build, shive-manager use cases.
merge
The ship gate — the only skill that merges. --staging merges the feature→staging PR on green CI, deploys, verifies, emits a human test script and stamps the staging sign-off on approval. --production ships the double-confirmed release to main and deploys production. Never self-certifies staging; nothing reaches main…
synthetic-release-notes
Draft release notes from user-provided changes.
land-and-deploy
Land and deploy workflow. Merges the PR, waits for CI and deploy, verifies production health via canary checks. Takes over after /ship creates the PR. Use when: "merge", "land", "deploy", "merge and verify", "land it", "ship it to production".
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.