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/agentculture/learn-cli/version-bumpnpx skills add agentculture/learn-cli --skill version-bumpgit clone --depth 1 https://github.com/agentculture/learn-cliWhat 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.00076 | $0.00668 |
| Opus 5 | $0.00038 | $0.00334 |
| Sonnet 5 | $0.00015 | $0.00134 |
| Haiku 4.5 | $0.00008 | $0.00067 |
Grade A, and why
version-bump 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 yesterday.
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.
This is a copy
100% identical to version-bump — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Version Bump
Bump the semver version in pyproject.toml and prepend a new entry to
CHANGELOG.md. Mirrors the AgentCulture workflow used by culture,
afi-cli, cfafi, and other org repos; vendored here so the repo is
self-contained.
Usage
Run from the repo root.
# With changelog content (pipe JSON via stdin):
echo '{"added":["New X"],"changed":["Refactored Y"],"fixed":["Bug in Z"]}' \
| python3 .claude/skills/version-bump/scripts/bump.py minor
# Without changelog content (inserts empty ### Added/Changed/Fixed stubs):
python3 .claude/skills/version-bump/scripts/bump.py patch
# Check current version without bumping:
python3 .claude/skills/version-bump/scripts/bump.py show
Bump Types
| Type | Example | When to use |
|---|---|---|
major |
0.1.0 → 1.0.0 | Breaking changes, namespace restructures, CLI surface breaks |
minor |
0.1.0 → 0.2.0 | New features, new commands, new modules |
patch |
0.1.0 → 0.1.1 | Bug fixes, doc updates, dependency bumps, CI-only changes |
show |
prints 0.1.0 |
Read-only — no files changed |
Changelog JSON Format
Pass via stdin. All fields are optional — only non-empty sections are rendered.
{
"added": ["List of new features"],
"changed": ["List of changes to existing functionality"],
"fixed": ["List of bug fixes"]
}
What it touches
pyproject.toml— theversion = "x.y.z"field (single source of truth;steward/__init__.pyreads it viaimportlib.metadata, so there's no separate__version__literal to keep in sync).CHANGELOG.md— inserts a new## [x.y.z] - YYYY-MM-DDentry at the top.
The script does the rest. Pick a bump type from the diff (patch for fixes,
minor for new features, major for breaking changes), summarize the diff into
added / changed / fixed lists, pipe as JSON, and commit the resulting
pyproject.toml + CHANGELOG.md alongside the code change so the
version-check CI job sees a consistent bump.
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.
- yesterday First seen · 68 lines · 76 tokens per session scan A 7a5af91e2626
version-bump is a skill published in the GitHub repository agentculture/learn-cli (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 76 tokens to every session and 668 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to version-bump, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…