agentmods.dev

bump-core-req

bump-core-req is a skill for Claude Code, Codex from gtapps/claude-code-hermit. It costs 139 tokens per session (1,424 once invoked), scanned A, original, MIT.

A procedure for raising the minimum supported core version of a fleet plugin, a plugin used across a group of related plugins. It updates the three project files where that requirement is recorded.

In plain words
What is it for?
It helps maintainers update a plugin's required core version across its metadata and dependency configuration.
Why use it?
It prevents the version requirement from becoming inconsistent between the runtime check, documentation, and plugin resolver. The change is prepared without committing it.

Skill for Claude CodeCodex

not rated 73 changed today A scan 139 tokens original MIT
View the source file gtapps/claude-code-hermit
Install

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.

agentmods
npx agentmods add skills/gtapps/claude-code-hermit/bump-core-req
Any agent
npx skills add gtapps/claude-code-hermit --skill bump-core-req
Clone the repo
git clone --depth 1 https://github.com/gtapps/claude-code-hermit

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for bump-core-req

README.md
[![agentmods](https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/bump-core-req.svg)](https://agentmods.dev/skills/gtapps/claude-code-hermit/bump-core-req)
Your own site
<a href="https://agentmods.dev/skills/gtapps/claude-code-hermit/bump-core-req"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/bump-core-req.svg" alt="Measured on agentmods" height="20"></a>
Per session 139 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,424 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00139 $0.01424
Opus 5 $0.00069 $0.00712
Sonnet 5 $0.00028 $0.00285
Haiku 4.5 $0.00014 $0.00142

Measured today against content hash 5d0ee2a891d2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 today.

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.

.agents/skills/bump-core-req/SKILL.md · 118 lines

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 (CLAUDE.md → Conventions), the core version requirement lives in:

  1. plugins/<slug>/.claude-plugin/hermit-meta.json → required_core_version — authoritative, read by doctor-check.ts at runtime to detect incompatible siblings
  2. plugins/<slug>/.claude-plugin/hermit-meta.json → requires["claude-code-hermit"] — documentation mirror
  3. plugins/<slug>/.claude-plugin/plugin.json → dependencies[name=claude-code-hermit].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 under plugins/ (e.g. claude-code-fitness-hermit)
  • [version] — optional target version like 1.0.26. If omitted, read plugins/claude-code-hermit/.claude-plugin/plugin.json → .version and use that.

Steps

Step 0: Resolve slug

If no slug was passed, or it's invalid:

  1. Glob plugins/*/.claude-plugin/plugin.json. Collect directory names.
  2. Remove claude-code-hermit from the list — that's core, not a fleet plugin.
  3. Ask via AskUserQuestion: "Which fleet plugin to update?" with one option per slug.

If claude-code-hermit 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 no hermit-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/claude-code-hermit/.claude-plugin/plugin.json → .version. This is the current shipped core version. Report it to the operator: "Autodetected core version: X.Y.Z".

Read the full file on GitHub · 118 lines

Changes

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.

  1. today Changed 5d0ee2a891d2
  2. 4d ago First seen · 118 lines · 139 tokens per session scan A dd469b9ecb46

Subscribe to this mod's changes

bump-core-req is a skill published in the GitHub repository gtapps/claude-code-hermit (73 stars, last pushed today), licensed MIT. It adds 139 tokens to every session and 1,424 once invoked, about $0.0007 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.

aiai-agentanthropicclaudeclaude-codeclaude-code-plugin
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens