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/liteagents --skill releasegit clone --depth 1 https://github.com/hamr0/liteagentsWrote 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/liteagents/release)<a href="https://agentmods.dev/skills/hamr0/liteagents/release"><img src="https://agentmods.dev/badge/skills/hamr0/liteagents/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/liteagents/release"><img src="https://agentmods.dev/badge/skills/hamr0/liteagents/release.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.00019 | $0.03809 |
| Opus 5.5 | $0.00008 | $0.01524 |
| Sonnet 5.5 | $0.00004 | $0.00762 |
| Haiku 4.5 | $0.00002 | $0.00381 |
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 19d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- release — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 244 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 its own
short mechanical checks, writes the CHANGELOG, 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. The general docs
sweep runs earlier, in /branch-review.
It does not review code. Review is a separate command that must have run first.
Guardrails
- Spawn a worker, mid tier stated explicitly (omitted inherits the parent's, not the balanced one; not cheapest/fastest either — judgment degrades there; never a vendor model name). 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.
- 19d ago Changed · +1 lines 8e8238b28545
- 20d ago Changed · +15 lines 1aad24169a46
- 21d ago Changed · +11 lines d6722fb4fda6
- 1mo ago Changed · +8 lines 9db232b55a9a
- 1mo ago Changed · +11 lines 1d69d7448be4
- 1mo ago Changed · -28 lines · +2 tokens per session be1bd1937a88
- 1mo ago Changed · +30 lines 07e23299b2e9
- 1mo ago First seen · 196 lines · 17 tokens per session scan A c38aa6213227
release is a skill published in the GitHub repository hamr0/liteagents (26 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 3,809 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-09-05.
Other skills, from other repositories
ship
Run a release end to end, autonomous by default: version bump everywhere, changelog, docs, landing page, tag, push, GitHub release, PyPI/npm. Use to ship, cut, or tag a release. Don't use for routine commits, pull requests, or marketplace publishing.
github-pages-publish
Publish or update a static site (gh-pages) on GitHub Pages via GitHub Actions in any repo: text or pre-built HTML in, workflow set up, live URL verified. Don't use for CI test pipelines, framework/SSG builds, or Netlify/Vercel hosting.
gem-release
Automates the complete process of releasing a new version of the openclacky Ruby gem. Supports both stable releases (auto-increment) and pre-release versions (user-specified, e.g., 1.0.0.beta.1). Handles version bumping, testing, building, RubyGems publishing, GitHub Releases, and OSS CDN mirroring.
lime-release-workflow
A release workflow for the Lime software project. It covers version numbers, release notes, cleaning generated files, required checks, commits, tags, and pushing changes.
cf-ship-custom
This is a version bump + ship + release operation. Run these steps BEFORE the standard cf-ship workflow.
cf-ship
Verify, commit, push, and create a PR. Triggers: "ship it", "push and create PR", "let's ship", "create a PR", "open a pull request", "ready to merge". Supports --dry-run.