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 thermiteau/maverick --skill mav-claude-code-recoverygit clone --depth 1 https://github.com/thermiteau/maverickWrote 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/thermiteau/maverick/mav-claude-code-recovery)<a href="https://agentmods.dev/skills/thermiteau/maverick/mav-claude-code-recovery"><img src="https://agentmods.dev/badge/skills/thermiteau/maverick/mav-claude-code-recovery/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/thermiteau/maverick/mav-claude-code-recovery"><img src="https://agentmods.dev/badge/skills/thermiteau/maverick/mav-claude-code-recovery.svg" alt="Reviewed on agentmods" width="80" 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.00043 | $0.01129 |
| Opus 5 | $0.00022 | $0.00564 |
| Sonnet 5 | $0.00009 | $0.00226 |
| Haiku 4.5 | $0.00004 | $0.00113 |
Grade A, and why
mav-claude-code-recovery 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 11d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Error Handling and Recovery
Patterns for making Claude Code workflows resilient to failures. This covers Claude Code's own recovery mechanisms, not error handling in generated application code.
Principles
- Persist state early and often — checkpoint progress after each phase so work can be resumed
- Post artefacts immediately — designs, plans, and status updates go to GitHub as soon as they are ready, not at the end
- Diagnose before retrying — when something fails, understand why before trying again
- Verify before continuing — on resume, confirm recorded state matches reality
- Isolate failures — subagent failures stay in the subagent; fix via a new subagent, not by polluting the main session
State Persistence
The maverick-task-progress marker on the GitHub issue is the single
state surface for issue-driven work (see
mav-github-issue-workflow): phase, branch, and artefact
comment ids, written via uv run maverick task-progress set after
each milestone completes — never before. Writing after completion means
the marker always reflects a consistent, completed milestone: if a
failure occurs mid-phase, the marker points at the last completed phase
and the incomplete phase re-executes from scratch.
Local files (worktrees, shortlists, diffs) are derivable caches. When a local artefact and GitHub disagree, GitHub wins.
Artefact Durability
Post artefacts to GitHub immediately after they are produced, via
uv run maverick issue comment post --kind <design|plan|tasks|completion>.
| Artefact | When |
|---|---|
| Solution design | Immediately after design is approved/produced |
| Implementation plan | Immediately after plan is approved/produced |
| Completion summary | After all steps pass verification |
| Blocking questions | When blocked and unable to resolve |
Batching artefacts to the end means a crash loses all intermediate work, the human has no visibility, and recovery re-does the design/planning.
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.
- 11d ago First seen · 109 lines · 43 tokens per session scan A 5f6fde071741
mav-claude-code-recovery is a skill published in the GitHub repository thermiteau/maverick (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 1,129 once invoked, about $0.0002 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-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.