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 skills add dmno-dev/bumpy --skill add-changegit clone --depth 1 https://github.com/dmno-dev/bumpyWrote 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/dmno-dev/bumpy/add-change)<a href="https://agentmods.dev/skills/dmno-dev/bumpy/add-change"><img src="https://agentmods.dev/badge/skills/dmno-dev/bumpy/add-change/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/dmno-dev/bumpy/add-change"><img src="https://agentmods.dev/badge/skills/dmno-dev/bumpy/add-change.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.00046 | $0.01296 |
| Opus 5.5 | $0.00018 | $0.00518 |
| Sonnet 5.5 | $0.00009 | $0.00259 |
| Haiku 4.5 | $0.00005 | $0.00130 |
Grade A, and why
add-change 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- add-change — 94% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a bumpy bump file
You are helping the user create a bumpy bump file — a markdown file in .bumpy/ that describes which packages changed and how. Bumpy uses these to bump versions and generate changelogs.
Steps
1. Gather context
First, understand what changed. Run these in parallel:
git diff --stat— see which files changedgit diff --cached --stat— see staged changesbumpy status --json— see if there are already pending bump files
If the user provided a description via $ARGUMENTS, use that as additional context for understanding the change.
Review the diff output to understand the scope of changes.
2. Identify affected packages
Determine which workspace packages are affected by the changes. Map changed files to their packages based on directory structure.
If unsure which packages exist, run:
bumpy status --packages 2>/dev/null || cat package.json
3. Determine bump levels
For each affected package, choose the appropriate bump level:
| Level | When to use |
|---|---|
| major | Breaking changes: removed/renamed exports, changed function signatures, dropped support |
| minor | New features: added exports, new options, new functionality |
| patch | Bug fixes, internal refactors, documentation, dependency updates |
Use none in a bump file to acknowledge a change without triggering a direct bump. Cascading bumps from other packages can still apply normally.
4. Write a clear summary
Write a concise summary for the CHANGELOG entry. Keep it short — ideally a single sentence, at most two. Good summaries:
- Start with a verb: "Added...", "Fixed...", "Refactored..."
- Focus on user-facing impact, not implementation details
- Are specific enough to be useful months later
- Avoid filler, jargon, or restating the bump level
- Don't list every file changed — describe the logical change
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 · 131 lines · 46 tokens per session scan A 32a718c69096
add-change is a skill published in the GitHub repository dmno-dev/bumpy (149 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 1,296 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-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.
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.
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.
updater_guide
Guidance for checking for and installing Row-Bot updates.