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/kyleve/stuff/upgrade-where-backupnpx skills add kyleve/Stuff --skill upgrade-where-backupgit clone --depth 1 https://github.com/kyleve/StuffWrote 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/kyleve/stuff/upgrade-where-backup)<a href="https://agentmods.dev/skills/kyleve/stuff/upgrade-where-backup"><img src="https://agentmods.dev/badge/skills/kyleve/stuff/upgrade-where-backup.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.00067 | $0.00491 |
| Opus 5 | $0.00034 | $0.00246 |
| Sonnet 5 | $0.00013 | $0.00098 |
| Haiku 4.5 | $0.00007 | $0.00049 |
Grade A, and why
upgrade-where-backup 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.
What it actually says
Upgrade a Where backup
Read the root AGENTS.md, Where/AGENTS.md, and Where/WhereCore/AGENTS.md.
Load the running-tests skill. Verification must run through ./test.
Run the bundled driver from the repository root:
ruby .agents/skills/upgrade-where-backup/scripts/upgrade_and_verify.rb INPUT [OUTPUT]
INPUT may be an unpacked backup directory or ZIP. OUTPUT defaults to a
sibling named <input>-upgraded.zip. The driver:
- Reads the source manifest and records the counts that migration must preserve.
- Creates a temporary input ZIP when necessary.
- Runs the repository's pinned Ruby and
Where/Tools/upgrade-backup.rb. - Checks ZIP integrity, the current manifest version, required tables, and counts.
- Writes the backup path and expected counts to a temporary JSON configuration.
- Enables and runs
BackupServiceTests.upgradedBackupDecodesAndLoadsAssetsthrough./test, exercisingBackupService.readArchive(at:)and all referenced asset bytes. The test is compiled but disabled during normal runs.
Keep every manifest transformation in Where/Tools/upgrade-backup.rb. The
driver only packages input, invokes that authority, and independently verifies
its output. Do not duplicate migration rules in the skill.
Safety and recovery
- Never modify or delete the input.
- Do not pass
--forceunless the user explicitly approves replacing the exact output path. Without it, an existing output is rejected. - Expect filesystem approval when the output is outside the workspace.
- The upgraded ZIP remains available if Swift verification fails. Diagnose the failure. Do not represent the backup as verified.
Handoff
Report the output path, source and destination format versions, preserved record counts, ZIP result, Ruby regression result, Swift production-decoder result, and whether the repository is clean. Do not expose backup contents in logs or the response.
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.
- 4d ago First seen · 48 lines · 67 tokens per session scan A 90596e0f9080
upgrade-where-backup is a skill published in the GitHub repository kyleve/Stuff (3 stars, last pushed today), licensed Apache-2.0. It adds 67 tokens to every session and 491 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…