Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/gtapps/hermitdnpx agentmods add skills/gtapps/hermitd/fleet-releaseWrote 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/gtapps/hermitd/fleet-release)<a href="https://agentmods.dev/skills/gtapps/hermitd/fleet-release"><img src="https://agentmods.dev/badge/skills/gtapps/hermitd/fleet-release/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/gtapps/hermitd/fleet-release"><img src="https://agentmods.dev/badge/skills/gtapps/hermitd/fleet-release.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00096 | $0.01300 |
| Opus 5.5 | $0.00038 | $0.00520 |
| Sonnet 5.5 | $0.00019 | $0.00260 |
| Haiku 4.5 | $0.00010 | $0.00130 |
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 11d 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 — 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.
- 11d ago First seen · 125 lines · 96 tokens per session scan A acde28561110
fleet-release is a skill published in the GitHub repository gtapps/hermitd (79 stars, last pushed today), licensed MIT. It adds 96 tokens to every session and 1,300 once invoked, about $0.0004 per session on Opus 5.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-10-02.
Other skills, from other repositories
release
Bump a plugin's version, write a detailed changelog entry for the upgrade skill to consume, and commit+push. Takes a plugin slug argument identifying which plugin under plugins/ to release. Use this skill whenever the user says "release", "version bump", "cut a release", "changelog and push", or finishes a set of…
fleet-release
Use this skill whenever the user wants to release, ship, prep, or cut versions for two or more plugins together on the current branch. Trigger on phrasings like "release both plugins", "ship them together", "release all changed plugins", "fleet release", "multi-plugin release", "release in order", or "release…
release-status
Use this skill to answer "what's ready to ship?", "where does the release pipeline stand?", "any plugins awaiting tag?", or "give me a pipeline overview". Shows plugin versions, tags, commits ahead, unreleased changes, and core compatibility. Read-only.
ccc-rollback
Roll production back by picking a known-good commit or tag, creating atomic git revert commits, pushing them, redeploying through the $ccc-deploy runners, and verifying health. Use when a deploy is bad, production is broken, or the user asks to revert or roll back a release.
release
Automated release management - version updates, changelog generation, git tagging, and GitHub release creation.
release-plugin
Cut a cairn plugin release for a given MAJOR.MINOR.PATCH version, running every pre-flight and version gate before anything is changed or published.