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/gtapps/claude-code-hermit/fleet-releasenpx skills add gtapps/claude-code-hermit --skill fleet-releasegit clone --depth 1 https://github.com/gtapps/claude-code-hermitWhat 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.00096 | $0.01323 |
| Opus 5 | $0.00048 | $0.00661 |
| Sonnet 5 | $0.00019 | $0.00265 |
| Haiku 4.5 | $0.00010 | $0.00132 |
Grade A, and why
fleet-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.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fleet Release
Orchestrate a multi-plugin release: determines order, runs each plugin's /release prep sequentially, injects cross-plugin hermit-meta.json sync between core and domain plugins, tags each plugin on main.
Runs on main. Each plugin is committed, tagged, and pushed in order. No PR needed.
Usage
/fleet-release [slug1 slug2 ...] explicit list
/fleet-release auto-detect from current branch
/fleet-release --dry-run show plan, no file changes
Steps
1. Validate branch
Run git branch --show-current. If not on main or the repo's default branch: stop and tell the user to switch to main before running a fleet release.
1.5. Refresh the knowledge graph (fleet-wide)
/release only refreshes the root graph plus its own target plugin's graph (single-plugin scope). A fleet release touches multiple plugins at once, so refresh everything in one shot before the per-plugin /release runs:
bash scripts/graphify-refresh.sh
AST-only, no API cost. Skips silently if graphify isn't installed or the session is in a worktree; a single plugin's update failure warns and continues rather than aborting — a stale graph must never block a release.
2. Determine target plugins
Explicit slugs: validate each exists at plugins/<slug>/.claude-plugin/plugin.json. For any unknown slug, abort and list available slugs.
Auto-detect (no args): discover all slugs from ls plugins/ (never hardcode or rely on session context), then collect plugins where both:
- Files under
plugins/<slug>/changed on this branch vs base:git diff <base>..HEAD --name-only -- plugins/<slug>/is non-empty plugin.jsonversion is ahead of the last<slug>--v*tag — same "already-bumped" detection as/releasestep 2
Skip plugins with no plugin.json version or no tags (unstructured). Note skipped plugins in output.
If condition 1 holds but condition 2 does not (branch changes but version not bumped yet): include the plugin and note it will need a full /release prep run.
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.
- yesterday Changed · +10 lines d840f7f6c36c
- 3d ago First seen · 115 lines · 96 tokens per session scan A a81a0c94bcd5
fleet-release is a skill published in the GitHub repository gtapps/claude-code-hermit (73 stars, last pushed yesterday), licensed MIT. It adds 96 tokens to every session and 1,323 once invoked, about $0.0005 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
release-notes
Draft concise release notes.
greptimedb-release
Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…
store-update
在 CCX Desktop 发布后下载 Store MSIX 并生成发布公告。用户提到 Store 上架、MSIX、从 GitHub Release 下载 store.msix、发布后同步 Windows Store、从 release 填写商店更新内容时必须使用此技能。该技能会下载最新 GitHub Release 的 amd64/arm64 MSIX，校验 sha256，从 Release body 生成 Store listing releaseNotes 预览，并输出手动上传指引。.