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 bump-core-reqgit 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/bump-core-req)<a href="https://agentmods.dev/skills/gtapps/hermitd/bump-core-req"><img src="https://agentmods.dev/badge/skills/gtapps/hermitd/bump-core-req/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/bump-core-req"><img src="https://agentmods.dev/badge/skills/gtapps/hermitd/bump-core-req.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.00137 | $0.01392 |
| Opus 5.5 | $0.00055 | $0.00557 |
| Sonnet 5.5 | $0.00027 | $0.00278 |
| Haiku 4.5 | $0.00014 | $0.00139 |
Grade A, and why
bump-core-req 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bump-core-req
Update a fleet plugin's minimum core version in all three canonical locations.
Background: why three places?
Per this monorepo's conventions (AGENTS.md → Repository and architecture), the core version requirement lives in:
plugins/<slug>/.claude-plugin/hermit-meta.json→required_core_version— authoritative, read bydoctor-check.tsat runtime to detect incompatible siblingsplugins/<slug>/.claude-plugin/hermit-meta.json→requires["hermitd"]— documentation mirrorplugins/<slug>/.claude-plugin/plugin.json→dependencies[name=hermitd].version— native Claude Code resolver field
All three must stay in sync. This skill is the single operation that touches all of them atomically. It leaves committing to the operator via /commit.
Usage
/bump-core-req <fleet-slug> [version]
<fleet-slug>— directory name of the fleet plugin underplugins/(e.g.hermitd-fitness)[version]— optional target version like1.0.26. If omitted, readplugins/hermitd/.claude-plugin/plugin.json→.versionand use that.
Steps
Step 0: Resolve slug
If no slug was passed, or it's invalid:
- Glob
plugins/*/.claude-plugin/plugin.json. Collect directory names. - Remove
hermitdfrom the list — that's core, not a fleet plugin. - Ask via
AskUserQuestion: "Which fleet plugin to update?" with one option per slug.
If hermitd was explicitly passed as slug, abort: "Core doesn't depend on itself — pass a fleet plugin slug."
Validate plugins/<slug>/.claude-plugin/hermit-meta.json exists. If not:
Abort: "
<slug>has nohermit-meta.json— not a fleet plugin or migration is incomplete."
Step 1: Resolve target version
If version was passed as an argument, strip a leading v if present. Validate the result matches X.Y.Z (digits only, two dots). If it doesn't match, abort with a clear message.
If no version arg, read plugins/hermitd/.claude-plugin/plugin.json → .version. This is the current shipped core version. Report it to the operator: "Autodetected core version: X.Y.Z".
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 · 118 lines · 137 tokens per session scan A 46e0010d259c
bump-core-req is a skill published in the GitHub repository gtapps/hermitd (79 stars, last pushed today), licensed MIT. It adds 137 tokens to every session and 1,392 once invoked, about $0.0005 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…
atlas-changelog
Maintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to "log this change", "update changelog", "what changed", "change history".
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.
apex-status
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
secrets-scan
Scans git-tracked files for leaked secrets. Triggers - secrets scan, find credentials, leaked keys, security audit.