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 glebis/claude-skills --skill cull-release-publishgit clone --depth 1 https://github.com/glebis/claude-skillsWrote 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/glebis/claude-skills/cull-release-publish)<a href="https://agentmods.dev/skills/glebis/claude-skills/cull-release-publish"><img src="https://agentmods.dev/badge/skills/glebis/claude-skills/cull-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/glebis/claude-skills/cull-release-publish"><img src="https://agentmods.dev/badge/skills/glebis/claude-skills/cull-release-publish.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 Excessive Agency · line 34 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00040 | $0.00357 |
| Opus 5 | $0.00020 | $0.00179 |
| Sonnet 5 | $0.00008 | $0.00071 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
cull-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 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.
What it actually says
Cull Release Publish
Authority
An explicit “Release Cull patch|minor|major” or direct “Publish prepared Cull release X.Y.Z” request authorizes publication. Do not ask for another confirmation after gates pass. That authority does not waive or bypass any gate.
Implicit invocation is disabled. Without that explicit authority, stop before any tag, push, workflow dispatch, release, or tap mutation.
Publish
- Resolve the Cull checkout and parse one JSON envelope from
npm run release:cull -- state show --version "$VERSION" --json. - Require state
prepared, exact metadata, a clean release commit already pushed onmain, green required checks, active branch/tag protection, publication enablement, and no conflicting tag. - Create one annotated tag for the prepared commit and push that tag normally. Never move, replace, or force-push a tag.
- Watch the tag-bound GitHub release workflow. Never substitute a local build.
- Require the secret-free verifier's exact artifact inventory, signatures, notarization, checksums, and provenance before automatic publication.
- Wait for checksum-pinned Homebrew promotion and its audit/install/launch proof.
- Record evidence transitions through
publishedandhomebrew-promotedusing the repository CLI's state commands.
On failure, use cull-release-recover. Never delete or rewrite a tag, delete a release, replace published assets, bypass verification, or force workflow state.
What ships with it
1 file 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 · 35 lines · 40 tokens per session scan A 61feb9bca3a8
cull-release-publish is a skill published in the GitHub repository glebis/claude-skills (374 stars, last pushed 9d ago), licensed MIT. It adds 40 tokens to every session and 357 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-30.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.