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 ao92265/claude-code-playbook --skill retrygit clone --depth 1 https://github.com/ao92265/claude-code-playbookWrote 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/ao92265/claude-code-playbook/retry)<a href="https://agentmods.dev/skills/ao92265/claude-code-playbook/retry"><img src="https://agentmods.dev/badge/skills/ao92265/claude-code-playbook/retry.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.1 | $0.00134 | $0.00814 |
| Opus 5 | $0.00067 | $0.00407 |
| Sonnet 5 | $0.00027 | $0.00163 |
| Haiku 4.5 | $0.00013 | $0.00081 |
Grade A, and why
retry 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 7d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retry After an API Error / Outage
A transient Anthropic API failure (overload, 5xx, rate limit, network blip, or a full outage) aborts the turn mid-task. This skill cleanly resumes the work that got cut off — it does NOT start fresh and does NOT re-litigate decisions already made before the error.
First: is this actually a retry?
Only proceed if the last failure was infrastructure, not the work itself:
- ✅ Retry:
Overloaded,429/529,500/503,rate_limit,fetch failed,socket hang up, "Claude is down", the turn just stopped with no result. - ❌ Not a retry — that's a fix: a test failed, a build broke, wrong output, a logic bug. Don't blindly redo it; diagnose. Say so and switch to fixing.
If it's ambiguous, ask the user which it was before acting.
Procedure
-
Reconstruct where it died. Read the last few turns + any handoff/state (
.omc/state/,.omc/handoffs/, todos, open files) to find the exact action that was in flight when the error hit. Don't assume — verify against the actual repo/file state, since a partial write may have landed. -
Check for partial work.
git status --shortand inspect the target file(s). The failed action may have half-completed (a file written but not verified, a commit started). Reconcile before redoing, so you don't double-apply. -
Re-run only the cut-off action, not the whole task. Pick up from the last verified-complete step. If several steps remain, restate the short remaining list first so the user can confirm scope.
-
Verify end-to-end before claiming done (build/test as the project requires) — the interruption means nothing downstream was checked.
Surviving a LIVE outage (the wrapper)
This skill can't help while the API is actually down — the model isn't running to
invoke it. For that, use the shell wrapper, which relaunches the CLI with
exponential backoff and resumes via --continue:
~/.claude/scripts/claude-retry.sh [any normal claude args]
# e.g. ~/.claude/scripts/claude-retry.sh -p "finish the migration"
# ~/.claude/scripts/claude-retry.sh # interactive TUI
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.
- 7d ago First seen · 64 lines · 134 tokens per session scan A 8186fc3f4421
retry is a skill published in the GitHub repository ao92265/claude-code-playbook (10 stars, last pushed 21d ago), licensed MIT. It adds 134 tokens to every session and 814 once invoked, about $0.0007 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.
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…