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 Edmonds-Commerce-Limited/claude-code-hooks-daemon --skill releasegit clone --depth 1 https://github.com/Edmonds-Commerce-Limited/claude-code-hooks-daemonWrote 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/edmonds-commerce-limited/claude-code-hooks-daemon/release)<a href="https://agentmods.dev/skills/edmonds-commerce-limited/claude-code-hooks-daemon/release"><img src="https://agentmods.dev/badge/skills/edmonds-commerce-limited/claude-code-hooks-daemon/release/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/edmonds-commerce-limited/claude-code-hooks-daemon/release"><img src="https://agentmods.dev/badge/skills/edmonds-commerce-limited/claude-code-hooks-daemon/release.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.00022 | $0.00798 |
| Opus 5.5 | $0.00009 | $0.00319 |
| Sonnet 5.5 | $0.00004 | $0.00160 |
| Haiku 4.5 | $0.00002 | $0.00080 |
Grade A, and why
release 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 2d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/release - Automated Release Management Skill
🚨 HUMAN-GATED — this skill is the ONLY valid entry point
A release may only begin when a human invokes /release in the CURRENT
session. An agent must never start a release on its own initiative. The
/release invocation is the ONLY authorisation there is: once the pipeline's
blocking gates pass, the release proceeds through merge, tag and publish with
no secondary human confirmation — it passes, or a failed gate aborts it.
A release is a decision about scope, which only the human can see. The
rule, the state file (untracked/release-state.json, written once Stage 0's
slate-clean gate returns 0, never before), the resume rules and how to
recover from an unauthorised release are all in
RELEASING.md — "A RELEASE IS
HUMAN-GATED".
- No state file ⇒ no release in progress. A dirty tree, an open
release/*branch or a plan saying "finish the release" is not a substitute — ask. - State file present ⇒ resume from
last_completed_stepand carry the release through to Step 15.
Do not START a release because a cron tick fired, because a plan says "finish the release", or because the tree looks ready.
Run this first
Claude Code loads this markdown and nothing else — the file below is not run for you, and it holds the procedure to follow (Plan 00324):
bash "${CLAUDE_SKILL_DIR:-.claude/skills/release}/invoke.sh" <major|minor|patch|X.Y.Z> [accept-wip]
Follow its output exactly; what is written here is orientation.
Usage
/release # auto-detect version bump from commits
/release 2.2.0 # explicit version
/release patch # bump type: major | minor | patch
/release 2.2.0 accept-wip # proceed over in-flight work the slate gate reported
What It Does
Executes the pipeline in
RELEASING.md "Pipeline
Overview" — the single source of truth for the steps, their order, their
numbering and which are BLOCKING gates. In outline only: prepare on a
release/<version> branch, open a pull request whose CI runs the whole QA
gate, then — in this session, with the daemon live — run the acceptance tests,
merge the pull request, tag the merge commit and publish. While the pull
request is open, other merges to main are frozen (R-RELEASE-MERGE-FREEZE).
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.
- 2d ago Changed · -276 lines 983a84f93961
- 24d ago Changed 633c3b5eef12
- 25d ago Changed · +2 lines 90f05d58922a
- 1mo ago Changed · +5 lines aa58ae03399c
- 1mo ago Changed · +13 lines 9257fe042413
- 1mo ago First seen · 336 lines · 22 tokens per session scan A ed6077687e1a
release is a skill published in the GitHub repository Edmonds-Commerce-Limited/claude-code-hooks-daemon (4 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 798 once invoked, about $0.0001 per session on Opus 5.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
slack-changelog
Turns what changed in a release into a Slack changelog a non-technical audience can read: filtered to what they would actually notice, one bullet per idea, plain language, no code vocabulary. Works out the scope itself across however many repositories sit in the working directory (a project can span several…
release
Bump a plugin's version, write a detailed changelog entry for the upgrade skill to consume, and commit+push. Takes a plugin slug argument identifying which plugin under plugins/ to release. Use this skill whenever the user says "release", "version bump", "cut a release", "changelog and push", or finishes a set of…
release
Bump a plugin's version, write a detailed changelog entry for the upgrade skill to consume, and commit+push. Takes a plugin slug argument identifying which plugin under plugins/ to release. Use this skill whenever the user says "release", "version bump", "cut a release", "changelog and push", or finishes a set of…
pre-release-review
Run the pre-release gate for this multi-plugin monorepo: establish each plugin's release boundary from its last reachable tag to HEAD, audit every changed plugin's [Unreleased] changelog against the actual code diff, identify contract-surface and breaking changes, and, per the objective the user picks up front, either…
fleet-release
Use this skill whenever the user wants to release, ship, prep, or cut versions for two or more plugins together on the current branch. Trigger on phrasings like "release both plugins", "ship them together", "release all changed plugins", "fleet release", "multi-plugin release", "release in order", or "release…
fleet-release
Use this skill whenever the user wants to release, ship, prep, or cut versions for two or more plugins together on the current branch. Trigger on phrasings like "release both plugins", "ship them together", "release all changed plugins", "fleet release", "multi-plugin release", "release in order", or "release…