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 hamr0/agentic-toolkit --skill releasegit clone --depth 1 https://github.com/hamr0/agentic-toolkitWrote 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/hamr0/agentic-toolkit/release)<a href="https://agentmods.dev/skills/hamr0/agentic-toolkit/release"><img src="https://agentmods.dev/badge/skills/hamr0/agentic-toolkit/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/hamr0/agentic-toolkit/release"><img src="https://agentmods.dev/badge/skills/hamr0/agentic-toolkit/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.00017 | $0.02839 |
| Opus 5 | $0.00009 | $0.01419 |
| Sonnet 5 | $0.00003 | $0.00568 |
| Haiku 4.5 | $0.00002 | $0.00284 |
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.
This is a copy
100% identical to release — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release preparation orchestrator for the current branch. It runs your existing pre-deploy gate, sweeps the docs, bumps the version and commits — then stops and reports. It never pushes, opens a PR, merges, tags, or publishes: those are yours to authorize by name.
It does not re-implement checks, and it does not review code. Review is a separate command that must have run first.
Guardrails
- Spawn a worker and explicitly select your tool's mid tier. State the tier on the spawn — do not omit it and rely on a default. An omitted tier inherits the parent's tier, which is not the same thing as the balanced one. Pick the judgment-capable tier that is cheaper and faster than your top reasoning tier. Not the cheapest/fastest tier: on judgment work it measurably degrades (misclassification rates several times higher). Choose by tier, not by a vendor model name copied from this file — names drift, and this command ships to several tools. Fall back to running inline if your tool has no subagent mechanism.
- Escalate, never assume. Anything you cannot decide, cannot verify, or that this spec does not cover → stop and report it to the orchestrator (the main session). Never improvise, never widen scope, never fix a finding you noticed along the way.
- Nothing leaves the machine. No
git push, nogh, nonpm publish, under any circumstance — not even if every gate is green. You report the sequence; a human authorizes it.
Phase 0 — Preflight (current branch, always)
- Release the branch you are on. No branch argument, no branch creation.
- On
main→ stop and ask what should be released.mainis only ever the merge target; never release it, never commit to it. - The tree must be clean — do not commit for the user. Run
git status --porcelain. Any line at all — modified, staged, or untracked — is a stop: list the paths and say "commit this to the branch, re-run/branch-review, then re-run/release." Committing here would create a commit after the review and so fail Phase 0.5 by its own rule on the very next step; a phase that guarantees the next phase fails is not a phase. git fetch origin; the release diff isorigin/main...HEAD. Empty → stop, nothing to release.- Record both version numbers. Read the local version (
package.jsonor this project's equivalent) and, if the project has a publish path, the published one (npm view <pkg> version, or the registry equivalent). Report them side by side. Local ahead of published means a version was cut on a branch and never published — Phase 3 cannot see that gap unless you record it here, and a worker that cannot see it will re-cut a number that already exists. - Print a one-line plan: branch · commit count · files changed · HEAD SHA · local version → published version.
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 First seen · 196 lines · 17 tokens per session scan A c38aa6213227
release is a skill published in the GitHub repository hamr0/agentic-toolkit (22 stars, last pushed 3d ago), licensed Apache-2.0. It adds 17 tokens to every session and 2,839 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to release, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
work
Dispatch a tracker ticket into an isolated worktree and drive it autonomously to an open pull request, then stop for review. Pass interactive to brainstorm the ticket with a human before planning it, or a sentence of editorial direction as a rider. Use when asked to work a ticket end-to-end.
batch
Dispatch a night's batch of Todo tickets — one worktree and one pull request each — and leave a morning summary. Run explicitly; never inferred.
linear-flow
Migrate a repo to the dev-trunk/main-release fast-forward model (no merge commits) and load its doctrine. One-shot setup; day-to-day rules live in each repo's CLAUDE.md afterwards.
await-merge
Wait for a PR's checks, merge it with linear history, update the local base branch.
github
Interact with GitHub using the gh CLI. Use for issues, PRs, CI runs, releases, and advanced API queries.
github-repo-management
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.