Borrowing it
Nothing to install: this file belongs to escapeWu/perplexity-ai. 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/escapeWu/perplexity-ai/main/.claude/skills/bump-version/SKILL.mdgit clone --depth 1 https://github.com/escapeWu/perplexity-aiWrote 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/escapewu/perplexity-ai/bump-version)<a href="https://agentmods.dev/skills/escapewu/perplexity-ai/bump-version"><img src="https://agentmods.dev/badge/skills/escapewu/perplexity-ai/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/escapewu/perplexity-ai/bump-version"><img src="https://agentmods.dev/badge/skills/escapewu/perplexity-ai/bump-version.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00049 | $0.00584 |
| Opus 5.5 | $0.00020 | $0.00234 |
| Sonnet 5.5 | $0.00010 | $0.00117 |
| Haiku 4.5 | $0.00005 | $0.00058 |
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 1mo 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.
What it actually says
Bump Version Skill
Steps
1. Determine new version
- User provides target version (e.g.
v1.9.0) - Strip the
vprefix for file edits
2. Update version files
pyproject.toml: updateversion = "x.x.x"perplexity/server/web/package.json: update"version": "x.x.x"— Vite reads this viavite.config.tsto inject__APP_VERSION__into the frontend build, which displays asMANAGER_vX.X.Xin the admin UI
3. Update changelogs
Add a new entry at the top of the changelog section in both files:
README.md — under ## Changelog:
+ **<YYYY-MM-DD>**: v<VERSION> — <summary in English>
README-zh.md — under ## 更新记录:
+ **<YYYY-MM-DD>**：v<VERSION> — <summary in Chinese>
Use today's date. Summarize the changes since the last version based on recent commits or what the user describes.
4. Build frontend
cd perplexity/server/web && npm run build
- If build succeeds: proceed to commit.
- If build fails: fix all TypeScript/lint errors in
perplexity/server/web/src/, then re-run the build until it passes. Do not proceed to commit until the build is green.
The dist/ folder is gitignored — do not force-add it.
5. Commit
Stage only source files (never dist/):
git add pyproject.toml README.md README-zh.md \
perplexity/server/web/package.json \
perplexity/server/web/src/
Also stage any other modified source files relevant to the release.
Commit message format:
feat: v<VERSION> - <short summary>
<bullet points of key changes>
Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
6. Tag and push
git tag v<VERSION>
git push origin main
git push origin v<VERSION>
Notes
- Always confirm the changelog summary with the user if the changes aren't obvious
- If the build fails, fix errors before committing
- Do not amend previous commits — always create a new commit
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.
- 1mo ago First seen · 72 lines · 49 tokens per session scan A 9cae58b50a7e
bump-version is a skill published in the GitHub repository escapeWu/perplexity-ai (177 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 584 once invoked, about $0.0002 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
Fully automate a release with version-bump and childhood.
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.
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.