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/jimmypaolini/codebase/restore-codenpx skills add JimmyPaolini/codebase --skill restore-codegit clone --depth 1 https://github.com/JimmyPaolini/codebaseWhat 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.01107 |
| Opus 5 | $0.00035 | $0.00553 |
| Sonnet 5 | $0.00014 | $0.00221 |
| Haiku 4.5 | $0.00007 | $0.00111 |
Grade A, and why
restore-code 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.
How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Restore Code From Backup
Recover code from backup artifacts with a preview-first workflow that minimizes additional loss.
When to Use This Skill
- After accidental destructive commands (
reset --hard,clean, force-overwrite checkouts) - After risky refactors or codemods introduced broad regressions
- After failed rebase or merge sequences where you need known-good state
- When files were deleted or overwritten and must be recovered quickly
- When a backup branch or stash exists and work must be restored safely
Keywords: restore code, recover backup, restore stash, recover branch snapshot, undo destructive change.
Recovery Sources Supported
- Backup branches (
backup/*) - Named stashes created for safety snapshots
- Specific commit snapshots (including backup commits)
- Selective file restore from any source reference
Prerequisites
- Run from repository root
gitis available- Backup source exists or can be discovered
- Working tree state is inspectable
Decision Flow
- If full workspace rollback is required, restore from backup branch.
- If local uncommitted work must be rehydrated, restore from stash.
- If only selected files are needed, perform selective file restore.
- If the target state is uncertain, preview diffs first and restore incrementally.
- If current work may still be needed, run
backup-codebefore restoring.
Step-by-Step Workflow
1. Inspect Current And Recovery State
Run:
git status --short
git branch --show-current
git branch --list "backup/*"
git stash list --date=local
Record:
- Current branch
- Current uncommitted changes
- Available backup branches
- Candidate stash entry IDs
2. Choose Recovery Strategy
Strategy A: Restore Entire State From Backup Branch
Preview:
git diff --stat HEAD..backup/<source-branch>/<source-iso-timestamp>
Restore via reset to backup commit (destructive to current local state):
git reset --hard backup/<source-branch>/<source-iso-timestamp>
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 · 175 lines · 70 tokens per session scan A b832fe4d48ad
restore-code is a skill published in the GitHub repository JimmyPaolini/codebase (0 stars, last pushed yesterday), licensed MIT. It adds 70 tokens to every session and 1,107 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-09-01.
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…