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 MartyBonacci/specswarm --skill ss-upgradegit clone --depth 1 https://github.com/MartyBonacci/specswarmWrote 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/martybonacci/specswarm/ss-upgrade)<a href="https://agentmods.dev/skills/martybonacci/specswarm/ss-upgrade"><img src="https://agentmods.dev/badge/skills/martybonacci/specswarm/ss-upgrade/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/martybonacci/specswarm/ss-upgrade"><img src="https://agentmods.dev/badge/skills/martybonacci/specswarm/ss-upgrade.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.00025 | $0.00579 |
| Opus 5 | $0.00013 | $0.00290 |
| Sonnet 5 | $0.00005 | $0.00116 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
ss-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 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpecSwarm Upgrade Workflow
Provides natural language access to /ss:upgrade command.
When to Invoke
Trigger this skill when the user mentions:
- Upgrading or updating dependencies/packages
- Migrating to new frameworks or versions
- Modernizing technology stacks
- Bumping version numbers
Examples:
- "Upgrade React to version 19"
- "Update all dependencies"
- "Migrate from Webpack to Vite"
- "Modernize the build system"
- "Bump Node to version 20"
Instructions
Skill-Based Routing:
-
Detect that user mentioned upgrading/updating software
-
Extract what to upgrade from their message
-
Route based on intent clarity:
Clear intent - Execute directly:
- Clear upgrade requests: "Upgrade React to version 19", "Update all dependencies", "Migrate from Webpack to Vite"
- Action: Immediately run
/ss:upgrade "upgrade description"
Ambiguous intent - Ask for confirmation:
- Less specific: "Update the packages", "Make it better"
- Action: Use AskUserQuestion tool with two options:
- Option 1 (label: "Run /ss:upgrade"): Use SpecSwarm's upgrade workflow with compatibility analysis
- Option 2 (label: "Process normally"): Handle as regular Claude Code request
-
If user selects Option 2, process normally without SpecSwarm
-
After command completes, STOP - do not continue with ship/merge
What the Upgrade Command Does
/ss:upgrade runs complete workflow:
- Analyzes breaking changes and compatibility
- Creates comprehensive upgrade plan
- Generates migration tasks
- Updates dependencies and code
- Runs tests to verify compatibility
- Documents upgrade process
Stops after upgrade is complete - does NOT merge/ship/deploy.
Semantic Understanding
This skill should trigger not just on exact keywords, but semantic equivalents:
Upgrade equivalents: upgrade, update, migrate, modernize, bump, move to, switch to, adopt Target terms: dependency, package, framework, library, version, technology stack
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 · 79 lines · 25 tokens per session scan A 1c3d090f249c
ss-upgrade is a skill published in the GitHub repository MartyBonacci/specswarm (65 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 579 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 skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.