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/escapewu/perplexity-ai/bump-versionnpx skills add escapeWu/perplexity-ai --skill bump-versiongit 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.svg" alt="Measured on agentmods" 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 | $0.00049 | $0.00584 |
| Opus 5 | $0.00024 | $0.00292 |
| Sonnet 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 5d 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.
- 5d 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 (165 stars, last pushed 16d ago), licensed MIT. It adds 49 tokens to every session and 584 once invoked, about $0.0002 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.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…