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 agentmods add skills/devstride/claude-plugin/updatenpx skills add devstride/claude-plugin --skill updategit clone --depth 1 https://github.com/devstride/claude-pluginWhat 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 | $0.00052 | $0.00516 |
| Opus 5 | $0.00026 | $0.00258 |
| Sonnet 5 | $0.00010 | $0.00103 |
| Haiku 4.5 | $0.00005 | $0.00052 |
Grade A, and why
update 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 yesterday.
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
Human output. Read ${CLAUDE_PLUGIN_ROOT}/skills/build-item/references/plain-language-output.md once per top-level run; composed skills reuse it. Apply it to every message.
This is a standalone user-authorized update, never a build-loop step. It may change the active user/project/local install. It may not change config, override a pin, guess between installs, remove/re-add a marketplace, or change an administrator-managed install.
Run exactly:
python3 "${CLAUDE_PLUGIN_ROOT}/skills/update/scripts/update-plugin.py" apply
The helper bypasses background-check caches and switches, finds the exact loaded copy, verifies the official tag and installed files, and checks disk again. Never substitute guessed commands or treat an exit code as proof.
Translate its one JSON result; never paste it raw:
updated/currentplussafeToReload: true: four short lines — Running, Installed, Install, Result. Explain user scope as shared on this machine; project/local as this repo only. Keep the exact id and scope in parentheses.blocked: explain the safety stop. Never bypass a pin, administrator boundary, duplicate, or missing repository binding.failed: say which stage failed and that success is unproved. IfmanualInspectionRequired, give no mutation command: Claude cannot prove which copy is safe to change. IfrepairRequired, do not reload or invoke another DevStride skill; separately ask permission to preserve data and reinstall, runrepairCommandsonly on yes, then rerun the helper. Otherwise give onlyretryCommandwhen present.
Only for updated/current with both safeToReload and reloadRequired true, finish:
Run /reload-plugins before another DevStride command and confirm it reports no DevStride load
error. If reload is unavailable or fails, restart Claude Code. Stop after this handoff.
The skill first exists in 3.1.0. Older copies need the README's two-command bootstrap once.
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.
- yesterday First seen · 42 lines · 52 tokens per session scan A 8e33f2dbbf38
update is a skill published in the GitHub repository devstride/claude-plugin (2 stars, last pushed 3d ago), licensed MIT. It adds 52 tokens to every session and 516 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…