Borrowing it
Nothing to install: this file belongs to mtarcure/claude-vibe-squad. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mtarcure/claude-vibe-squad/main/.agents/skills/take-over-resume/SKILL.mdgit clone --depth 1 https://github.com/mtarcure/claude-vibe-squadWrote 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/mtarcure/claude-vibe-squad/take-over-resume)<a href="https://agentmods.dev/skills/mtarcure/claude-vibe-squad/take-over-resume"><img src="https://agentmods.dev/badge/skills/mtarcure/claude-vibe-squad/take-over-resume/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/mtarcure/claude-vibe-squad/take-over-resume"><img src="https://agentmods.dev/badge/skills/mtarcure/claude-vibe-squad/take-over-resume.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00052 | $0.01309 |
| Opus 5 | $0.00026 | $0.00655 |
| Sonnet 5 | $0.00010 | $0.00262 |
| Haiku 4.5 | $0.00005 | $0.00131 |
Grade A, and why
take-over-resume 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Take-Over Resume
Resume work on a tree that a human may have changed while you were not looking. The failure mode is narrow and expensive: work resumes against a remembered state, the operator's manual fix is silently reverted or duplicated, and the conflict surfaces much later as a mysterious regression.
The controlling assumption is that the tree is the truth and your memory of it is a hypothesis.
When to use
- Resuming a task that was paused for manual intervention.
- Returning to a worktree after an operator hand-fix.
- Any resume where time has passed and the tree was reachable by someone else.
- A task that failed, was repaired by hand, and is being restarted.
Pausing cleanly
When work is being suspended for someone to intervene:
- Stop at a coherent point. Suspend between steps, not mid-write. A tree caught half way through a multi-file edit is one nobody can safely reason about.
- Record the resume anchor — the commit the work was built on, the tree involved, and the step that was about to run. This anchor is what makes the resume diff meaningful; without it, the diff has no baseline and the whole procedure degrades to guessing.
- State what is safe to touch, so intervention does not collide with in-flight state.
- Never remove a worktree with work still in flight. Removal kills the running work. Re-read in-flight status immediately before any cleanup, not from a status read earlier in the session.
Resuming
-
Diff against the anchor before reading anything else. List the changed files, then read the actual diff. This is the first action on resume — not a check performed after planning, because a plan built on the remembered tree is already wrong.
git diff <anchor>does not show untracked files, and a new file is the most common human edit. A file the human created is invisible to the diff alone, so the procedure would miss precisely the change that triggered it. Enumerate untracked paths separately and read them in full:
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 · 97 lines · 52 tokens per session scan A 7a07b64b2060
take-over-resume is a skill published in the GitHub repository mtarcure/claude-vibe-squad (148 stars, last pushed 2d ago), licensed MIT. It adds 52 tokens to every session and 1,309 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-30.
Other skills, from other repositories
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
cw-land
Use when turning verified Codewhale work into commits, branches, or a merge: choosing direct-main vs. worktree vs. integration branch, preserving contributor credit, and honoring the gate artifact before merging.
cw-orient
Use at the start of any Codewhale work session, or when unsure which checkout, branch, or worktree is authoritative: establish live repo truth before reading a plan or editing a file.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
contributor-onboarding
Help a new contributor get productive on this checkout - inspect sync state against main, build, run the repository's exact verification gate, and produce a local what's-new digest. Never fetches, pulls, or modifies a dirty tree on its own. Explicit-only.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.