Borrowing it
Nothing to install: this file belongs to kaininx/PlainTab. 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/kaininx/PlainTab/main/.agents/skills/bump-version/SKILL.mdgit clone --depth 1 https://github.com/kaininx/PlainTabWrote 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/kaininx/plaintab/bump-version)<a href="https://agentmods.dev/skills/kaininx/plaintab/bump-version"><img src="https://agentmods.dev/badge/skills/kaininx/plaintab/bump-version/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/kaininx/plaintab/bump-version"><img src="https://agentmods.dev/badge/skills/kaininx/plaintab/bump-version.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.00073 | $0.02539 |
| Opus 5.5 | $0.00029 | $0.01016 |
| Sonnet 5.5 | $0.00015 | $0.00508 |
| Haiku 4.5 | $0.00007 | $0.00254 |
Grade A, and why
bump-version 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 2mo 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bump PlainTab Version
Purpose
Prepare a PlainTab release using the current project structure. Keep the release surface split by audience:
docs/changelog-i18n/*.txt: one-line localized changelog summaries.docs/RELEASE_NOTES.md: historical detailed release notes, maintained only in Chinese and English.docs/GITHUB_RELEASE.md: the body text for the current GitHub Release page only.docs/store-listing/*.txt: Chrome Web Store descriptions, one file per language.
Do not recreate removed files such as docs/CHANGELOG.md, docs/release-note.md, or docs/requirements.md. Do not add a version badge to the root README.md; it intentionally does not use one. Localized docs/README_*.md files that already have version badges should keep that style and have the existing badge version updated.
Inputs
Ask for missing essentials only:
- Target version, for example
3.3.0. - Release summary in Chinese or English.
- Important changes, grouped as user-facing bullets. Conventional commit lines may be used as source material, but do not expose commit tags in user-facing docs unless the user explicitly asks.
If the user does not provide release notes, derive candidate changes from git log and local diffs, then write user-facing summaries.
Style Rules
- Preserve the current document style. Before writing release copy, inspect the newest entry in each touched file and match its punctuation, bullet shape, heading level, language register, and sentence length.
- Keep product copy user-facing. Translate implementation work into outcomes; do not paste raw commit subjects, module names, storage keys, or test names unless the user asks for maintainer-facing wording.
- Keep Chinese release copy in the existing concise PlainTab tone. Do not add marketing hype, emoji, slogans, or unrelated feature explanation.
- Keep English release copy in the existing calm, compact product tone. Do not switch to a different launch-note style mid-file.
- Keep commit style aligned with the current history: Chinese Conventional Commit subject by default, for example
docs: 更新版本发布资料orchore: 准备 X.Y.Z 发布. Do not switch to English, long titles, or a different body format unless the user asks.
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.
- 2mo ago First seen · 242 lines · 73 tokens per session scan A 55c346f45c12
bump-version is a skill published in the GitHub repository kaininx/PlainTab (96 stars, last pushed 5mo ago), licensed MIT. It adds 73 tokens to every session and 2,539 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
release
Fully automate a release with version-bump and childhood.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.