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/kitup/kitup-releasenpx skills add lathe-cli/kitup --skill kitup-releasegit clone --depth 1 https://github.com/lathe-cli/kitupWhat 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.00040 | $0.00408 |
| Opus 5 | $0.00020 | $0.00204 |
| Sonnet 5 | $0.00008 | $0.00082 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
kitup-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 yesterday.
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.
What it actually says
kitup Release
Use this only inside /Users/x/git/samzong/kitup or the upstream kitup repository.
Release Contract
Do not publish from a pull request. Do not tag the release branch.
The maintainer-owned flow is:
- Start from a clean, up-to-date
main. - Run one release prep command:
make release-patch
make release-minor
make release-major
- Let the command create
release/vX.Y.Z, update versions, runmake check, and commitchore: prepare vX.Y.Z release. - Ask the maintainer to open and merge the release PR manually.
- After merge, the maintainer tags
mainmanually:
git checkout main
git pull --ff-only
git tag vX.Y.Z
git push origin vX.Y.Z
Version Surfaces
Release prep must keep these in sync:
ts/package.jsonpython/pyproject.tomlpython/uv.lockexamples/python/uv.lockrust/Cargo.tomlrust/Cargo.lockexamples/rust/Cargo.lockgo-cobra/go.mod
Automation
The root vX.Y.Z tag triggers .github/workflows/release.yml. The workflow runs make check, verifies package versions, publishes npm, PyPI, and crates.io packages, creates go/vX.Y.Z and go-cobra/vX.Y.Z, creates GitHub Release notes, and runs scripts/smoke-release.sh X.Y.Z.
If a registry already accepted a version, do not delete and recreate tags without an explicit recovery plan.
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.
- yesterday First seen · 54 lines · 40 tokens per session scan A e46a757466de
kitup-release is a skill published in the GitHub repository lathe-cli/kitup (6 stars, last pushed 4d ago), licensed Apache-2.0. It adds 40 tokens to every session and 408 once invoked, about $0.0002 per session on Opus 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-08-31.
Other skills, from other repositories
remotion-bits
Animation components and utilities for Remotion video projects. Use when building Remotion compositions with text animations, gradient transitions, particle effects, 3D scenes, or staggered motion effects. Provides example bits (complete compositions) and reusable components that can be installed via jsrepo.
remotion-animation
Generates animation configurations for Remotion including spring configs, interpolations, easing functions, and timing logic. Focuses ONLY on animation parameters, NOT component implementation. Use when defining animation behavior or when asked to "configure animations", "setup spring configs", "define easing curves".
modern-short-video
Create modern product launch/pitch videos using Remotion. Use when creating app promo videos, SaaS launch videos, product demos, or startup pitch videos.
video-production
Produce programmable videos with Remotion using scene planning, asset orchestration, and validation gates for automated, brand-consistent video content.
better-fullstack
Scaffold, plan, or extend Better Fullstack projects with the generator, CLI, or MCP server. Use when a user asks to create, generate, or scaffold a fullstack starter; choose a Better Fullstack stack; add Better Fullstack capabilities; compare agent scaffolding paths; or avoid hand-authoring boilerplate project files.
create-remotion-geist
Create Remotion videos using the Geist design system aesthetic. Use when asked to create videos, animations, or motion graphics that should follow Vercel's visual style - dark theme, spring animations, Geist typography, and the Geist color palette.