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.
git clone --depth 1 https://github.com/secondsky/claude-skillsWrote 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/commands/secondsky/claude-skills/bun-upgrade)<a href="https://agentmods.dev/commands/secondsky/claude-skills/bun-upgrade"><img src="https://agentmods.dev/badge/commands/secondsky/claude-skills/bun-upgrade.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.1 | $0.00010 | $0.00922 |
| Opus 5 | $0.00005 | $0.00461 |
| Sonnet 5 | $0.00002 | $0.00184 |
| Haiku 4.5 | $0.00001 | $0.00092 |
Grade A, and why
bun:upgrade 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 8d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bun Upgrade Helper
Upgrade Bun runtime and project dependencies safely.
Upgrade Options
Upgrade Bun Runtime
# Upgrade to latest stable
bun upgrade
# Upgrade to specific version
bun upgrade --version 1.0.0
# Upgrade to canary
bun upgrade --canary
Check current version:
bun --version
Upgrade Dependencies
# Check for outdated
bun outdated
# Update all dependencies
bun update
# Update specific package
bun update react
# Update to latest (ignore semver)
bun update --latest
Interactive Upgrade
Check what will change:
# See what would update
bun outdated
# Review changes before applying
bun update --dry-run
Breaking Changes Check
Before upgrading, check for breaking changes:
Bun Changelog
Major breaking changes by version:
- 1.0 - Stable API, may break pre-1.0 code
- 1.1 - Windows support added, cross-platform Bun Shell, WebSocket client stabilized
- 1.2 - NEW: Text-based lockfile format (bun.lock), built-in S3/Postgres APIs, Node.js 90% compatibility
⚠️ v1.2 Lockfile Change: Binary bun.lockb → Text bun.lock (JSONC format)
- Easier to read, review PRs, and resolve merge conflicts
- Cached installs 30% faster than v1.1
- Migration happens automatically on first
bun installwith v1.2
Dependency Breaking Changes
Check changelogs for major version bumps:
# See current vs latest
bun outdated
# For each major bump, review:
# - GitHub releases
# - CHANGELOG.md
# - Migration guides
Safe Upgrade Process
-
Backup current state
git add -A && git commit -m "Pre-upgrade checkpoint" -
Check what's outdated
bun outdated -
Upgrade Bun first
bun upgrade -
Test with current deps
bun test -
Upgrade dependencies
bun update -
Run tests again
bun test -
Verify build
bun run build
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.
- 8d ago First seen · 211 lines · 10 tokens per session scan A 806e93b849e5
bun:upgrade is a command published in the GitHub repository secondsky/claude-skills (215 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 922 once invoked, about $0.0001 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 commands, from other repositories
correlate
Find related failures through pattern matching.
diff
Compare two command outputs with intelligent diff.
open
Open/retrieve an offloaded output by ID or shortcut.
search
Search through offloaded outputs with hard caps.
stats
Show FewWord session statistics with rich output and token savings.
timeline
Visual timeline of command outputs in current session.