resume-pipeline

resume-pipeline is a skill for Claude Code from ai-analyst-lab/ai-analyst. It costs 19 tokens per session (303 once invoked), scanned A, original, MIT.

A controlled way to continue one specific analysis that was interrupted or previously failed. It checks the run's inputs, state, and files before continuing.

In plain words
What is it for?
Use it to resume a selected run, investigate failures before retrying, handle approval checkpoints, and continue valid completed work.
Why use it?
It avoids resuming the wrong analysis or using outdated files. It also prevents unsafe retries and reports the actual final result.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to resume a selected run, investigate failures before retrying, handle approval checkpoints, and continue valid completed work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ai-analyst-lab/ai-analyst/resume-pipeline
Install

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.

Any agent
npx skills add ai-analyst-lab/ai-analyst --skill resume-pipeline
Clone the repo
git clone --depth 1 https://github.com/ai-analyst-lab/ai-analyst

Made for: Claude Code.

Wrote 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.

agentmods badge for resume-pipeline

README.md
[![agentmods](https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst/resume-pipeline/github.svg)](https://agentmods.dev/skills/ai-analyst-lab/ai-analyst/resume-pipeline)
Your own site
<a href="https://agentmods.dev/skills/ai-analyst-lab/ai-analyst/resume-pipeline"><img src="https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst/resume-pipeline/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.

agentmods 80×15 button for resume-pipeline

Your own site · 80×15
<a href="https://agentmods.dev/skills/ai-analyst-lab/ai-analyst/resume-pipeline"><img src="https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst/resume-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 303 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.00303
Opus 5 $0.00010 $0.00151
Sonnet 5 $0.00004 $0.00061
Haiku 4.5 $0.00002 $0.00030

Measured 2d ago against content hash c00c1aaa6a3a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-13, from the pricing page.

Security

Grade A, and why

resume-pipeline 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 2d 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.

.claude/skills/resume-pipeline/SKILL.md · 27 lines

What it actually says

Resume the requested analysis

  1. Identify the exact run. Inspect question, inputs, plan and status. If several match, ask which one. A latest link does not select the user's intended work.
  2. Version 3 state uses helpers.pipeline.controller.Controller. Never overwrite or reinterpret legacy state as version 3. Offer a new run with explicitly selected, verified legacy artifacts while retaining the originals.
  3. For blocked approval gates, show evidence and request approval. Record it only after receiving it, with checkpoint, actor and reason. Local records are not authenticated identities.
  4. For failures, inspect the cause before retrying. Confirm an interrupted worker is no longer running. Never remove a lock while another controller is active.
  5. Run python -m helpers.pipeline.controller run EXACT_RUN_DIRECTORY, with --retry-failed only for an intentional retry. Code validates definition and artifact hashes and skips valid completed work. Changed definitions/artifacts require a new reviewed run; do not silently reuse stale work.
  6. Report the actual final status and outputs. Never manually change statuses or create a deck for a plan that did not request one.

Authentication, tool permissions and workflow approvals are separate requirements. See docs/PIPELINE-CONTROLLER.md for recovery and migration details.

Changes

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.

  1. 2d ago First seen · 27 lines · 19 tokens per session scan A c00c1aaa6a3a

Subscribe to this mod's changes

resume-pipeline is a skill published in the GitHub repository ai-analyst-lab/ai-analyst (298 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 303 once invoked, about $0.0001 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-12.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

microsoft/vscode · 72 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens