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/jumpstarter-dev/jumpstarter/releasenpx skills add jumpstarter-dev/jumpstarter --skill releasegit clone --depth 1 https://github.com/jumpstarter-dev/jumpstarterWhat 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.00021 | $0.05588 |
| Opus 5 | $0.00010 | $0.02794 |
| Sonnet 5 | $0.00004 | $0.01118 |
| Haiku 4.5 | $0.00002 | $0.00559 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 478 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jumpstarter Release
You are guiding the user through the Jumpstarter project release process.
Before proceeding, read .claude/rules/releasing-operator.md for operator-specific details.
Release input: $ARGUMENTS
Conventions
- Git tags use a
vprefix:v0.8.1,v0.9.0-rc.1 - Container image tags do NOT use a
vprefix::0.8.1,:0.9.0-rc.1 - RC tag format:
vX.Y.Z-rc.N(with dot before N). Reject old formats likerc1or-rc1. - RC-first rule: When a release branch has no final release tags yet, the first tag MUST be an RC. Never tag a direct
vX.Y.0final on a new branch without at least one RC first. - FLS tags do NOT use a
vprefix:0.3.0,0.4.0(repo:jumpstarter-dev/fls) - Python packages are versioned automatically from git tags via
hatch-vcs— no manual version files. - The
bundle/directory is NOT committed to the repo. GITHUB_USERenv var controls the fork for community-operators and for pushing version-bump PRs. Auto-detected viagh api user -q .loginif not set.- Do NOT modify
controller/deploy/operator/api/v1alpha1/jumpstarter_types.go— the operator resolves:latestimage defaults to its own version at runtime.
Ordering constraint
[optional FLS release] → Makefile/FLS pin update → commit → tag push → GitHub Release / [CI builds images] → make bundle → make contribute
If a new FLS version is needed, release FLS first so binaries exist before Jumpstarter CI builds the exporter image. Images must exist before bundle generation. The skill enforces this by splitting the process into phases.
Steps
1. Gather context and determine release type
Fetch the latest remote state and detect the GitHub user early:
GITHUB_USER="${GITHUB_USER:-$(gh api user -q .login)}"
echo "GitHub user: $GITHUB_USER"
git fetch origin --tags
git branch --show-current
git branch -r | grep 'origin/release-'
git tag --sort=-version:refname | head -20
gh release list --limit 5
grep -E '^(VERSION|REPLACES) ' controller/deploy/operator/Makefile
# Current FLS pins in Jumpstarter
grep -E 'ARG FLS_VERSION=' python/Containerfile
rg -n 'fls_version: str = "|--fls-version"' \
python/packages/jumpstarter-driver-flashers/jumpstarter_driver_flashers/client.py
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.
- 2d ago First seen · 478 lines · 21 tokens per session scan A 11a882a7d969
release is a skill published in the GitHub repository jumpstarter-dev/jumpstarter (214 stars, last pushed 2d ago), licensed Apache-2.0. It adds 21 tokens to every session and 5,588 once invoked, about $0.0001 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-30.
Other skills, from other repositories
gh-issues
Walk over all open GitHub issues that are unassigned or assigned to the current user, and process each one via the /gh-issue skill, sequentially.
pr
Push branch and create a GitHub PR with concise, issue-linked description.
commit
Stage and commit changes using conventional commits format.
gh-issue
Fetch GitHub issue, create branch, plan and implement with TDD, then open PR.
release
Run pre-release validation and execute the release process.
pre-release
Run comprehensive pre-release validation checklist.