lathe-release

lathe-release is a skill for Claude Code, Codex from lathe-cli/lathe. It costs 48 tokens per session (3,453 once invoked), scanned C, original, Apache-2.0.

A release-checking workflow for Lathe, a software project with versioned releases. It validates a proposed version before it is tagged or published.

In plain words
What is it for?
Checking a release candidate, running regression tests, preparing release files, and publishing a Lathe version when explicitly requested.
Why use it?
It reduces the risk of shipping a release with failing tests, incorrect version details, or missing release checks.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/lathe-cli/lathe/lathe-release
Any agent
npx skills add lathe-cli/lathe --skill lathe-release
Clone the repo
git clone --depth 1 https://github.com/lathe-cli/lathe

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 lathe-release

README.md
[![agentmods](https://agentmods.dev/badge/skills/lathe-cli/lathe/lathe-release.svg)](https://agentmods.dev/skills/lathe-cli/lathe/lathe-release)
Your own site
<a href="https://agentmods.dev/skills/lathe-cli/lathe/lathe-release"><img src="https://agentmods.dev/badge/skills/lathe-cli/lathe/lathe-release.svg" alt="Measured on agentmods" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,453 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
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 $0.00048 $0.03453
Opus 5 $0.00024 $0.01726
Sonnet 5 $0.00010 $0.00691
Haiku 4.5 $0.00005 $0.00345

Measured 4d ago against content hash 9c3c5508fa07, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

lathe-release scanned grade C with 1 finding 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 4d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf "$ROOT/$EX/internal/generated" "$ROOT/$EX/skills" "$ROOT/$EX/bin" "$ROOT/$EX/go.sum"
.agents/skills/lathe-release/SKILL.md · 265 lines

How it starts

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

Lathe Release

Contract

Start read-only. Read repo-local instructions first: AGENTS.md, CLAUDE.md, CONTRIBUTING.md, release docs, Makefile, CI, and release config. Trust live code/config over old docs.

Default to validation only. Do not create tags, commits, pushes, PRs, or GitHub releases unless the user explicitly asks to cut/publish/release the target version.

Require a concrete semantic target version before candidate validation or publishing. If the version is missing or conflicts with existing tags/releases, ask one question.

Use ignored scratch paths for generated validation artifacts. Create a unique .local/regression-$VERSION.XXXXXX/ directory and use ignored release output such as dist/.

Use rtk for commands when available. If rtk blocks a command, run the command raw and report the fallback.

Release Flow

  1. Confirm target version and current baseline.
  2. Check worktree cleanliness and current branch.
  3. Fetch tags and verify the target tag does not exist locally or remotely.
  4. Read release workflow config and CI status for HEAD.
  5. Run the repo's declared local gate plus release-specific artifact dry-run.
  6. Run product-specific end-to-end smoke tests.
  7. Report ready, blocked, or ready with skipped checks.
  8. Only if explicitly asked to publish: create the tag, push it, then monitor the release workflow.

Never claim a release is ready without fresh command output from this run.

Lathe Pre-Release Gate

Use this section in a Lathe checkout. Derive the baseline from the latest release and validate the current tracked product surfaces; do not copy assumptions from a version-named scratch directory.

Live State

set -euo pipefail
SEMVER_RE='^v(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)(-((0|[1-9][0-9]*|[0-9]*[A-Za-z-][0-9A-Za-z-]*)(\.(0|[1-9][0-9]*|[0-9]*[A-Za-z-][0-9A-Za-z-]*))*))?(\+([0-9A-Za-z-]+(\.[0-9A-Za-z-]+)*))?$'
if ! printf '%s\n' "${VERSION:-}" | grep -Eq "$SEMVER_RE"; then
  echo "VERSION must be a semantic version such as v0.6.0" >&2
  exit 2
fi
git status --short --branch
git fetch origin --tags --prune
gh release list --limit 10
git tag --list 'v*' --sort=-v:refname | head -20
git ls-remote --tags origin "refs/tags/$VERSION"
gh run list --commit "$(git rev-parse HEAD)" --limit 6 --json databaseId,headSha,event,status,conclusion,workflowName,createdAt,updatedAt

Read the full file on GitHub · 265 lines

Files

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.

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. 4d ago First seen · 265 lines · 48 tokens per session scan C 9c3c5508fa07

Subscribe to this mod's changes

lathe-release is a skill published in the GitHub repository lathe-cli/lathe (48 stars, last pushed 4d ago), licensed Apache-2.0. It adds 48 tokens to every session and 3,453 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

skmtc-architecture

Understand what SKMTC is, how its engine works, and the architectural invariants — for agents building or extending infrastructure around SKMTC rather than authoring generators or running the CLI. Covers the three-phase pipeline, the host/Worker boundary, cross-generator coordination, the manifest, the attribution /…

skmtc/skmtc · 240 tokens

skmtc-debug

Diagnose failures in SKMTC sessions — no output, wrong output, error messages, bundle freshness, parseIssues, "Registered definition mismatch", ref cycles, "Module not found" in generated code, or any other broken behavior. Applies across both CLI usage and generator authoring contexts. Use this skill when the user…

skmtc/skmtc · 213 tokens

skmtc-lang-kotlin

The Kotlin target-language layer for Skmtc generators (@skmtc/lang-kotlin): base factories, KtSnippet, the seven entity kinds, packages-from-paths imports, the head+value render model, KtAnnotation and the composition classes, sanitization and @SerialName placement, plus the current-API worked example (the shipped…

skmtc/skmtc · 117 tokens

skmtc-retro-review

Aggregate friction log files across a time period to identify recurring patterns, classify each cluster by intervention type, produce a prioritized action plan with success criteria, and calculate convergence metrics. Complements skmtc-retro (which captures per-session signal) by acting as the system's actuator…

skmtc/skmtc · 211 tokens

skmtc-retro

Run a self-retrospective on a SKMTC-related session — generator authoring, CLI configuration, debugging, or any sustained interaction involving @skmtc/core, @skmtc/cli, or @skmtc/gen- packages. Captures three distinct outputs: (1) friction entries (mistakes, surprises, overridden defaults, multi-cycle struggles), (2)…

skmtc/skmtc · 311 tokens

skmtc-generator

Author and edit Skmtc generators — packages that project an OpenAPI domain model into application code. Method: clone the nearest stock generator, then apply the engine rules imitation can't teach. Assumes zero prior Skmtc knowledge. Use when asked to "write a skmtc generator", "author/clone/customize gen-x", "add a…

skmtc/skmtc · 110 tokens