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 agentmods add skills/lathe-cli/lathe/lathe-releasenpx skills add lathe-cli/lathe --skill lathe-releasegit clone --depth 1 https://github.com/lathe-cli/latheWrote 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/lathe-cli/lathe/lathe-release)<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>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 | $0.00048 | $0.03453 |
| Opus 5 | $0.00024 | $0.01726 |
| Sonnet 5 | $0.00010 | $0.00691 |
| Haiku 4.5 | $0.00005 | $0.00345 |
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" 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
- Confirm target version and current baseline.
- Check worktree cleanliness and current branch.
- Fetch tags and verify the target tag does not exist locally or remotely.
- Read release workflow config and CI status for
HEAD. - Run the repo's declared local gate plus release-specific artifact dry-run.
- Run product-specific end-to-end smoke tests.
- Report
ready,blocked, orready with skipped checks. - 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
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.
- 4d ago First seen · 265 lines · 48 tokens per session scan C 9c3c5508fa07
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.
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-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-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-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-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-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…