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 ScriptedAlchemy/agent-bundle --skill dependency-upgradegit clone --depth 1 https://github.com/ScriptedAlchemy/agent-bundleWrote 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/scriptedalchemy/agent-bundle/dependency-upgrade)<a href="https://agentmods.dev/skills/scriptedalchemy/agent-bundle/dependency-upgrade"><img src="https://agentmods.dev/badge/skills/scriptedalchemy/agent-bundle/dependency-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/scriptedalchemy/agent-bundle/dependency-upgrade"><img src="https://agentmods.dev/badge/skills/scriptedalchemy/agent-bundle/dependency-upgrade.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.00029 | $0.00336 |
| Opus 5.5 | $0.00012 | $0.00134 |
| Sonnet 5.5 | $0.00006 | $0.00067 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
dependency-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 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.
What it actually says
Dependency upgrade
Match the user's scope: a plan or compatibility review does not authorize implementation, rollout, or publication. For implementation, complete the requested upgrade and relevant validation before reporting it done.
Use the compatibility checklist to select checks for affected surfaces. For a proposal or rollout handoff, use the upgrade plan template; mark unavailable evidence explicitly rather than inventing a result or owner.
Workflow
- Record the current and proposed versions, why the change is needed, and the supported runtime/package-manager matrix.
- Read primary release notes and migration guides. List removed APIs, default changes, peer requirements, and known regressions that intersect this repo.
- Map affected imports, configuration, generated artifacts, consumers, and CI/release surfaces before editing.
- When implementation is requested, make the smallest coherent change and run checks that exercise its affected behavior. Include builds or packed-consumer checks when emitted or published output is affected.
- For release readiness, record rollout signals, rollback evidence, and real consumer verification. A planning task can finish with a concrete plan and clearly identified validation still needed before rollout.
Final answer
State the compatibility decision, changed surfaces, evidence run, remaining risk, rollout signal, and exact rollback trigger. Mark any item not yet available for the requested scope.
What ships with it
2 files 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.
- 1mo ago Changed · +1 tokens per session 9141a3a71f08
- 1mo ago Changed · +2 lines · +10 tokens per session 0a9584e832bf
- 1mo ago First seen · 34 lines · 18 tokens per session scan A 3528992c7671
dependency-upgrade is a skill published in the GitHub repository ScriptedAlchemy/agent-bundle (11 stars, last pushed 9d ago), licensed Apache-2.0. It adds 29 tokens to every session and 336 once invoked, about $0.0001 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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…