Borrowing it
Nothing to install: this file belongs to PaulRBerg/prb-effect. 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/PaulRBerg/prb-effect/main/.agents/skills/release-and-bump/SKILL.mdgit clone --depth 1 https://github.com/PaulRBerg/prb-effectWrote 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/paulrberg/prb-effect/release-and-bump)<a href="https://agentmods.dev/skills/paulrberg/prb-effect/release-and-bump"><img src="https://agentmods.dev/badge/skills/paulrberg/prb-effect/release-and-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/paulrberg/prb-effect/release-and-bump"><img src="https://agentmods.dev/badge/skills/paulrberg/prb-effect/release-and-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.00064 | $0.01003 |
| Opus 5 | $0.00032 | $0.00502 |
| Sonnet 5 | $0.00013 | $0.00201 |
| Haiku 4.5 | $0.00006 | $0.00100 |
Grade A, and why
release-and-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 9d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release and Bump
End-to-end pipeline: release a @prb/effect-* package to npm, bump it in the consumer monorepo (~/sablier/new-ui),
migrate any breaking changes or new features.
Step 1: Identify Package
If $ARGUMENTS contains a package name, use it directly. Otherwise, infer from the current working directory by reading
package.json — if it has a name starting with @prb/effect-, use that.
If neither provides a package name (e.g., cwd is the monorepo root and no argument was given), ask the user which
package to release using AskUserQuestion with these options:
- @prb/effect-evm
- @prb/effect-evm-safe
- @prb/effect-next
- @prb/effect-solana
- @prb/effect-xstate
Then cd into the package directory before continuing.
Step 2: Run release commands (publish from package directory)
Run the release bump + push flow first:
zsh -ic 'ccbump <package-name>'
git push origin
Then run npm publish from within the released package's directory:
cd <package-directory>
eval "$(direnv export zsh)"
npm publish
npm publish MUST run from the package directory (e.g., evm-safe/ for @prb/effect-evm-safe), not the monorepo root.
If any command exits with a non-zero code, stop and report the error. Do not proceed.
Step 3: Verify npm Publication
Read package.json to get the new version (ccbump modifies it in Step 2).
Verify the package is available on npm:
npm view <package-name>@<new-version> version
If the command fails (package not yet propagated), wait 10 seconds and retry once:
sleep 10 && npm view <package-name>@<new-version> version
If still failing after the retry, warn the user that npm propagation is slow but continue to the next step — the version was published successfully if Step 2 succeeded.
Step 4: Bump in ~/sablier/new-ui
Delegate to the node-deps-bumper skill to update the package version in the consumer monorepo:
- Change directory:
cd ~/sablier/new-ui - Invoke:
/node-deps-bumper <package-name>
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.
- 9d ago First seen · 117 lines · 64 tokens per session scan A dded7d705a1b
release-and-bump is a skill published in the GitHub repository PaulRBerg/prb-effect (22 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 1,003 once invoked, about $0.0003 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
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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
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.
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.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
updater_guide
Guidance for checking for and installing Row-Bot updates.