release-llama-launcher

release-llama-launcher is a skill for Claude Code, Codex from airiclenz/llama-launcher. It costs 141 tokens per session (2,389 once invoked), scanned A, original, MIT.

A release procedure for llama-launcher, a software project. It checks release requirements, prepares notes and version information, creates local release commits, and publishes only after a dry run and explicit confirmation.

In plain words
What is it for?
It helps prepare and publish a version, confirm the version and release notes with the owner, run a dry run, and bring the release channels together.
Why use it?
It separates reviewable preparation from the irreversible publishing step and prevents a blocked release check from being bypassed.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: names the AskUserQuestion tool.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is go run ./cmd/release status --json > "$S" || true.

Good fit It helps prepare and publish a version, confirm the version and release notes with the owner, run a dry run, and bring the release channels together.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/airiclenz/llama-launcher
agentmods
npx agentmods add skills/airiclenz/llama-launcher/release-llama-launcher

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for release-llama-launcher

README.md
[![agentmods](https://agentmods.dev/badge/skills/airiclenz/llama-launcher/release-llama-launcher/github.svg)](https://agentmods.dev/skills/airiclenz/llama-launcher/release-llama-launcher)
Your own site
<a href="https://agentmods.dev/skills/airiclenz/llama-launcher/release-llama-launcher"><img src="https://agentmods.dev/badge/skills/airiclenz/llama-launcher/release-llama-launcher/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.

agentmods 80×15 button for release-llama-launcher

Your own site · 80×15
<a href="https://agentmods.dev/skills/airiclenz/llama-launcher/release-llama-launcher"><img src="https://agentmods.dev/badge/skills/airiclenz/llama-launcher/release-llama-launcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 141 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,389 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00141 $0.02389
Opus 5.5 $0.00056 $0.00956
Sonnet 5.5 $0.00028 $0.00478
Haiku 4.5 $0.00014 $0.00239

Measured 2d ago against content hash dba36697a5ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

release-llama-launcher 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.

skills/release-llama-launcher/SKILL.md · 193 lines

How it starts

The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release llama-launcher — cut and publish a release

Mission

Turn everything shipped since the last published release — the whole history before the first one — into a published release: notes the owner approved, a version the owner confirmed, and every channel converged. The deterministic work belongs to go run ./cmd/release (ADR-0017: .capcom/knowledge/decisions/adr-0017.md, or capcom know show adr-0017; the runbook is docs/releasing.md); this skill does the judgment and the asking.

The optional argument vX.Y.Z (a bare X.Y.Z reads the same) is a version proposal — the owner still confirms it in step 4. VERSION holds the bare X.Y.Z; the tag is v + VERSION.

In this repository this skill and release-notes-llama-launcher replace the personal cut-release and release-notes skills: those stand aside here, and neither is run for llama-launcher.

Boundaries

  • One irreversible step: publish. Everything before it is local and undone with git reset --keep HEAD~2; everything after it is fixed forward, never undone.
  • No bypass. A blocked gate stops the run. You never tag, push, create a GitHub release, or commit to the tap by hand — publish does all of it, and the tag is made by CI, never by you or publish.
  • Ask with the host's user-question tool (ask_user, AskUserQuestion, or similar) at every Ask below, and wait for the answer. No answer, or a host without the tool, means stop — never assume consent.
  • Needs an authenticated gh (gh auth status) and a Go toolchain. Shell snippets assume fail-fast hosts (set -e, pipefail): a command that may match nothing carries || true — keep it.

1 — Status and resume check (one shell call)

T="$(git rev-parse --show-toplevel)"; cd "$T"
TMP="${TMPDIR:-${TEMP:-/tmp}}"; S="$TMP/release-llama-launcher-status.json"
go run ./cmd/release status --json > "$S" || true
echo "TMP=$TMP"; echo "VERSION=$(cat VERSION)"; git log -2 --format=%s

Read $S yourself (it is small). Its keys: version, highestTag, gate.{ok,failures}, baseline.{tag,published,range,commits}, steps[].{name,state,detail}. A missing or unparsable file → stop and relay the command's error (likely gh unauthenticated or no network).

Read the full file on GitHub · 193 lines

Changes

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.

  1. 2d ago First seen · 193 lines · 141 tokens per session scan A dba36697a5ca

Subscribe to this mod's changes

release-llama-launcher is a skill published in the GitHub repository airiclenz/llama-launcher (2 stars, last pushed 3d ago), licensed MIT. It adds 141 tokens to every session and 2,389 once invoked, about $0.0006 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-10-14.