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-preparegit 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-prepare)<a href="https://agentmods.dev/skills/glebis/claude-skills/cull-release-prepare"><img src="https://agentmods.dev/badge/skills/glebis/claude-skills/cull-release-prepare/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-prepare"><img src="https://agentmods.dev/badge/skills/glebis/claude-skills/cull-release-prepare.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00043 | $0.00331 |
| Opus 5 | $0.00022 | $0.00166 |
| Sonnet 5 | $0.00009 | $0.00066 |
| Haiku 4.5 | $0.00004 | $0.00033 |
Grade A, and why
cull-release-prepare 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.
What it actually says
Cull Release Prepare
Principle
Prepare one reproducible release commit.
Preparation cannot tag, push, dispatch workflows, publish, or update Homebrew.
Required inputs
- An explicit
patch|minor|major; never infer the bump. - Green cull-release-check evidence bound to
expectedSourceandexpectedVersion. - Curated release notes and compatibility-review JSON matching Cull's CLI schema.
Prepare
- Fetch
origin/mainand create a dedicated clean worktree from it. Preserve unrelated dirty worktrees. - Confirm the check evidence still matches HEAD and the expected next version.
- Store curated notes in a safely quoted path. Use argument arrays or separately quoted variables; never evaluate a concatenated command.
- Run the dry run first:
npm run release:cull -- prepare ... --dry-run --json. - Parse exactly one JSON envelope. Continue only when it lists exactly the configured version, changelog, compatibility, and state files.
- Run the same prepare command without
--dry-run. - Verify one
chore(release): vX.Y.Zcommit, stateprepared, the declared file set, no tag, and no remote mutation.
On failure, show diagnostics and changed files. Never reset, discard, or overwrite work outside the release-owned file set.
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.
- 12d ago First seen · 37 lines · 43 tokens per session scan A c0a9c8d69776
cull-release-prepare is a skill published in the GitHub repository glebis/claude-skills (375 stars, last pushed 9d ago), licensed MIT. It adds 43 tokens to every session and 331 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.