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 skills add gtapps/hermitd --skill releasegit clone --depth 1 https://github.com/gtapps/hermitdWrote 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/release)<a href="https://agentmods.dev/skills/gtapps/hermitd/release"><img src="https://agentmods.dev/badge/skills/gtapps/hermitd/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/release"><img src="https://agentmods.dev/badge/skills/gtapps/hermitd/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.00104 | $0.03882 |
| Opus 5.5 | $0.00042 | $0.01553 |
| Sonnet 5.5 | $0.00021 | $0.00776 |
| Haiku 4.5 | $0.00010 | $0.00388 |
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 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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
Bump version, write changelog, commit, and push for a single plugin in the monorepo. The changelog entry is critical because the upgrade skill (skills/hermit-evolve/SKILL.md) reads it to know what to tell hermits during /hermitd:hermit-evolve.
Usage
/release <plugin-slug> — release the plugin at plugins/<plugin-slug>/.
Examples:
/release hermitd— release the core plugin/release hermitd-dev— release the dev hermit/release hermitd-homeassistant— release the HA hermit/release hermitd-laravel-forge— release the Laravel Forge hermit
If invoked without a slug, list all plugins/<name>/ directories that contain .claude-plugin/plugin.json and ask the operator which one via AskUserQuestion before proceeding.
Steps
0. Identify target plugin
Resolve the plugin slug:
- If the user passed
<slug>as argument, use that. - Otherwise, glob
plugins/*/.claude-plugin/plugin.json, collect the directory names, and ask via AskUserQuestion: "Which plugin to release?" with one option per slug.
Validate plugins/<slug>/.claude-plugin/plugin.json exists. If it does not, abort: Plugin 'plugins/<slug>/' not found. Suggest the available slugs.
Throughout the rest of this skill, $PLUGIN_DIR refers to plugins/<slug>/.
1. Pre-release validation
Run before anything else. Abort the release if any step fails.
-
Run the native plugin validator (CLI form):
claude plugin validate plugins/<slug> 2>&1Abort on any error.
-
Run test suites for the target plugin. Detect the convention and dispatch:
- If
plugins/<slug>/tests/run-all.shexists (bash entrypoint, used by dev/fitness/scribe/forge):bash plugins/<slug>/tests/run-all.sh 2>&1 - Else if any
plugins/<slug>/tests/*.test.tsexists (bun entrypoint, used by core/HA):cd plugins/<slug> && bun test 2>&1 - Else if a
plugins/<slug>/tests/dir exists but neither marker matched: abort the release withPlugin '<slug>' has a tests/ dir but no recognized convention (run-all.sh or *.test.ts) — fix the dispatch before releasing.Do not silently skip. - Else (no
tests/dir at all): skip this step and note it in the release report.
- If
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 · 252 lines · 104 tokens per session scan A a8acc1251a0d
release is a skill published in the GitHub repository gtapps/hermitd (79 stars, last pushed today), licensed MIT. It adds 104 tokens to every session and 3,882 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
git-flow
Use when creating a branch, using worktrees for parallel work, committing, or wrapping up. Covers branch naming, conventional commits, short-lived branches, worktree isolation, and final merge/cleanup.
changelog
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
git-workflow
Git operations: commits, branches, PRs, and conflict resolution.
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…