Borrowing it
Nothing to install: this file belongs to pandazki/pneuma-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/pandazki/pneuma-skills/main/.agents/skills/bump/SKILL.mdgit clone --depth 1 https://github.com/pandazki/pneuma-skillsWrote 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/pandazki/pneuma-skills/bump)<a href="https://agentmods.dev/skills/pandazki/pneuma-skills/bump"><img src="https://agentmods.dev/badge/skills/pandazki/pneuma-skills/bump/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/pandazki/pneuma-skills/bump"><img src="https://agentmods.dev/badge/skills/pandazki/pneuma-skills/bump.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.00032 | $0.02836 |
| Opus 5.5 | $0.00013 | $0.01134 |
| Sonnet 5.5 | $0.00006 | $0.00567 |
| Haiku 4.5 | $0.00003 | $0.00284 |
Grade A, and why
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 12d 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/bump — Version Bump & Release
Perform a full version bump: sync main, write changelog, refresh top-level docs, bump version, and push.
Read references/release-process.md before executing the steps; it owns the detailed release checklist and recovery notes. Paths in this procedure are repository-relative unless marked as skill-relative.
Steps
1. Sync main
Inspect the branch, status, and diff first. Preserve unrelated work. Include the
current task's authorized changes in the release; do not ask the user to resolve
your own pending edits. Fetch origin and compare the intended release with
origin/main. Fast-forward when possible; use an isolated checkout if unrelated
edits prevent a safe update. Resolve routine integration issues within scope and
ask only when including or changing unrelated work requires a decision.
2. Determine version bump
Review all commits since the last version tag to decide the bump level per Semantic Versioning:
- patch (x.y.Z): bug fixes, minor improvements, doc updates
- minor (x.Y.0): new features, new modes, new API endpoints, new viewer capabilities
- major (X.0.0): breaking changes to contracts, CLI interface, or manifest format
Read the current version from package.json. Compute the new version. If unsure, ask the user.
3. Write CHANGELOG entry
Read CHANGELOG.md and the git log since the last version bump commit. Write a new version section at the top following the existing format:
## [X.Y.Z] - YYYY-MM-DD
### Added
- ...
### Fixed
- ...
### Improved
- ...
Rules:
- Group changes by category (Added / Fixed / Improved / Changed / Removed)
- Each bullet should be a concise, user-facing description — not a commit message copy
- Bold the feature name, then describe what it does
- Omit categories with no entries
- Do NOT include chore/CI/version-bump commits
4. Refresh top-level docs
Review README.md, README.zh.md, AGENTS.md, and docs/reference/project-guide.md against the current codebase state. Fix any contradictions, outdated info, or missing features. This is a holistic review, not just appending — trim stale content, update tables, fix version numbers.
What ships with it
2 files 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.
- 12d ago Changed · +3 lines 7e20b27162cb
- 15d ago Changed · +7 lines d1c7cce01775
- 19d ago Changed · +2 lines aa621fb76713
- 1mo ago Changed · +34 lines db4dec424506
- 1mo ago Changed · -4 lines 00f8c4a0d721
- 1mo ago Changed bf96d571fc12
- 1mo ago First seen · 207 lines · 32 tokens per session scan A 4690f6703e54
bump is a skill published in the GitHub repository pandazki/pneuma-skills (161 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 2,836 once invoked, about $0.0001 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-09-11.
Other skills, from other repositories
omh-deploy-and-monitor
This is an OMH deploy-and-monitor workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
omh-release-cut
This is an OMH release-cut workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
release-engineering
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering from a bad deploy, or defining release…
release-rollback
Plan and execute authorized release promotion or rollback with exact artifact and data compatibility. Use when deploying versions, changing traffic or recovering a bad release; do not equate reversing code with restoring data.