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/release-statusnpx skills add gtapps/claude-code-hermit --skill release-statusgit clone --depth 1 https://github.com/gtapps/claude-code-hermitWrote 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/claude-code-hermit/release-status)<a href="https://agentmods.dev/skills/gtapps/claude-code-hermit/release-status"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/release-status.svg" alt="Measured on agentmods" 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 | $0.00083 | $0.01128 |
| Opus 5 | $0.00042 | $0.00564 |
| Sonnet 5 | $0.00017 | $0.00226 |
| Haiku 4.5 | $0.00008 | $0.00113 |
Grade A, and why
release-status 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 4d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Status
Read-only diagnostic — git status for the release pipeline. No mutations.
Steps
1. Collect plugin data
Glob plugins/*/.claude-plugin/plugin.json. For each slug:
# version
jq -r .version plugins/<slug>/.claude-plugin/plugin.json
# last tag (double-dash format)
git tag --list "<slug>--v*" | sort -V | tail -1
# commits since last tag, scoped to this plugin's directory
# use HEAD as base if no tag exists
git rev-list <last-tag-or-HEAD>..HEAD --count -- plugins/<slug>/
# non-empty [Unreleased] section
awk '/^## \[Unreleased\]/{flag=1; next} /^## \[/{flag=0} flag && NF' \
plugins/<slug>/CHANGELOG.md
# hygiene: duplicate section headers inside [Unreleased] (fragmented changelog
# from parallel worktree merges)
awk '/^## \[Unreleased\]/{f=1; next} /^## \[/{f=0} f && /^### /' \
plugins/<slug>/CHANGELOG.md | sort | uniq -d
# hygiene: merges since last tag that touched the plugin but not its CHANGELOG
# (likely missing an [Unreleased] entry; use the repo's initial commit if no tag)
git log --merges --format=%H <last-tag-or-initial>..HEAD -- plugins/<slug>/ | while read m; do
git diff --name-only "$m^1" "$m" -- plugins/<slug>/CHANGELOG.md | grep -q . \
|| git log -1 --format='%h %s' "$m"
done
For plugins with no plugin.json version or no recognizable tags: mark as unstructured (skip) and stop collecting data for that plugin.
2. Get latest core reference
git tag --list "claude-code-hermit--v*" | sort -V | tail -1
Extract just the version number (strip claude-code-hermit--v). Call it latest_core_version.
3. Read dependency constraints (domain plugins only)
For each plugin that has plugins/<slug>/.claude-plugin/hermit-meta.json:
jq -r .required_core_version plugins/<slug>/.claude-plugin/hermit-meta.json
4. Determine status per plugin
| Condition | Status |
|---|---|
plugin.json version > last tag version |
awaiting-tag |
[Unreleased] section is non-empty |
prep-needed |
version matches last tag, no [Unreleased] |
up-to-date |
| no version or no tags | unstructured |
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.
- 4d ago First seen · 100 lines · 83 tokens per session scan A 534e23a4f8d4
release-status is a skill published in the GitHub repository gtapps/claude-code-hermit (73 stars, last pushed today), licensed MIT. It adds 83 tokens to every session and 1,128 once invoked, about $0.0004 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
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
codex-test-gen
Generate unit tests for specified functions using Codex MCP.
brand-docx
Brand-aware Word engine. Use to (1) EXTRACT a company's brand from a Word template into a reusable "Brand Profile", (2) COMPREHEND the template with the model (optional), (3) VERIFY it, (4) GENERATE new on-brand .docx documents FROM a saved profile. Trigger on "extract our brand", "learn/match this template", "use our…
extract-resume
Parse a resume's uploaded PDF into structured JSON (basics, experience, projects, skills, education) and save it to the editor.