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-checkgit 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-check)<a href="https://agentmods.dev/skills/glebis/claude-skills/cull-release-check"><img src="https://agentmods.dev/badge/skills/glebis/claude-skills/cull-release-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/glebis/claude-skills/cull-release-check"><img src="https://agentmods.dev/badge/skills/glebis/claude-skills/cull-release-check.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.00036 | $0.00325 |
| Opus 5 | $0.00018 | $0.00162 |
| Sonnet 5 | $0.00007 | $0.00065 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
cull-release-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.
What it actually says
Cull Release Check
Principle
Treat Cull's JSON release CLI as authoritative. This skill is strictly read-only.
Run the check
- Resolve the checkout: current Git repository when its origin matches
glebis/cull; otherwise absoluteCULL_REPO; otherwise$HOME/ai_projects/cull. - Require an explicit
patch|minor|majoronly when calculating a new target. Otherwise inspect the current candidate. - Capture
git status --porcelainandgit rev-parse HEAD. - Run
npm run release:cull -- check --bump "$KIND" --jsonfrom the checkout. - Parse exactly one JSON envelope from stdout. Treat extra stdout, invalid JSON, or a nonzero exit as a blocker.
- Capture status and HEAD again. If either changed, return
CHECK_MUTATED_REPOSITORYand stop.
Report contract
Report current and target versions, source SHA, branch and sync state, disk, toolchains, contract gates, CI, secret presence, and every blocker. Report secret presence only; never print environment values or secret contents.
Mutation boundary
Run no preparation, commit, tag, push, workflow dispatch, publication, Homebrew promotion, installation, or recovery apply action. If the CLI proposes one, report it without executing it.
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 · 37 lines · 36 tokens per session scan A c3d957e4115f
cull-release-check is a skill published in the GitHub repository glebis/claude-skills (374 stars, last pushed 9d ago), licensed MIT. It adds 36 tokens to every session and 325 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.