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/jerry0022/dotclaude/auto-updatenpx skills add Jerry0022/dotclaude --skill auto-updategit clone --depth 1 https://github.com/Jerry0022/dotclaudeWrote 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/jerry0022/dotclaude/auto-update)<a href="https://agentmods.dev/skills/jerry0022/dotclaude/auto-update"><img src="https://agentmods.dev/badge/skills/jerry0022/dotclaude/auto-update.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 | $0.00070 | $0.01335 |
| Opus 5 | $0.00035 | $0.00668 |
| Sonnet 5 | $0.00014 | $0.00267 |
| Haiku 4.5 | $0.00007 | $0.00134 |
Grade A, and why
auto-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 4d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Update
Manually trigger a plugin update with user-facing reporting.
Architecture
The actual update logic lives in ss.plugin.update.js (SessionStart hook).
This skill is a thin wrapper that:
- Captures the current state (version, SHA)
- Runs the hook's JS code (pull + cache rebuild + registry update + verify)
- Reports what changed (changelog, verify status)
No duplicated logic. The hook is the single source of truth for the update mechanism. This skill only adds reporting.
Constants
PLUGIN_ROOT = ${CLAUDE_PLUGIN_ROOT} (from hook environment)
MARKETPLACE_DIR = ~/.claude/plugins/marketplaces/dotclaude
PLUGIN_SUBDIR = plugins/devops
HOOK_SCRIPT = ${PLUGIN_ROOT}/hooks/session-start/ss.plugin.update.js
Step 0 — Capture current state + channel
- Read current version from
MARKETPLACE_DIR/PLUGIN_SUBDIR/.claude-plugin/plugin.json - Read current git SHA:
git -C MARKETPLACE_DIR rev-parse --short HEAD - Read the channel pin from
~/.claude/plugins/.channels.json(key = marketplace name, missing/invalid →stable). One channel per MARKETPLACE — a single clone cannot serve two plugins on different channels. --channel <alpha|beta|stable>flag: re-pin by writing the sidecar ({"dotclaude": "beta"}merged into the existing JSON), then continue with the update so the new pin takes effect immediately.- Compute drift: latest version visible to the pin vs. latest alpha
(
git -C MARKETPLACE_DIR ls-remote --tags origin, numeric compare onalpha/vX.Y.Z/beta/vX.Y.Z/stable/vX.Y.Z/ barevX.Y.Z). - Report:
Currently installed: v{version} ({sha}) — Channel: {channel}, latest visible: v{N}and, when alpha is ahead:(alpha has v{M} available).
Step 1 — Run update hook
Execute the hook script directly:
node HOOK_SCRIPT
The hook handles:
- Channel-aware update on all marketplace clones (ring model): once a
stable/*tag exists, the clone is pinned to the highest version visible to the channel pin via a detached tag checkout; before that, a bootstrap fallback keeps the legacygit pull --ff-onlybehavior - Cache rebuild (recursive copy incl. dotfiles)
installed_plugins.jsonregistry update (incl. informationalchannel)- Silent verification (version alignment, cache completeness)
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.
- 4d ago First seen · 151 lines · 70 tokens per session scan A efb5f4178742
auto-update is a skill published in the GitHub repository Jerry0022/dotclaude (5 stars, last pushed yesterday), licensed MIT. It adds 70 tokens to every session and 1,335 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…