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 kaisa-kucherenko/claude-code-flow --skill pickupgit clone --depth 1 https://github.com/kaisa-kucherenko/claude-code-flowWrote 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/kaisa-kucherenko/claude-code-flow/pickup)<a href="https://agentmods.dev/skills/kaisa-kucherenko/claude-code-flow/pickup"><img src="https://agentmods.dev/badge/skills/kaisa-kucherenko/claude-code-flow/pickup.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.00106 | $0.00555 |
| Opus 5 | $0.00053 | $0.00278 |
| Sonnet 5 | $0.00021 | $0.00111 |
| Haiku 4.5 | $0.00011 | $0.00056 |
Grade A, and why
pickup 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.
What it actually says
Pickup — continue from a handoff
Find the file
/pickup <slug|issue|topic>— match against handoff filenames./pickupbare: glob the project root forHANDOFF_*.md.- Exactly one → proceed.
- Several → show a compact list: filename, header topic, last-updated date, first line of its NEXT section — ask which to pick up.
- None → say so; don't invent a handoff.
- An @-mention that failed to attach (typo like
HENDOFF) is still a pickup request — glob and read the file yourself.
Verify before acting — never execute a handoff blindly
The file records conclusions as of its write time; ground truth may have moved. Before starting:
- Compare its recorded branch/HEAD/commit hashes against
git log— flag commits that appeared since, or a recorded HEAD that is gone. - Spot-check that key files/artifacts it names still exist.
- If it lists verification commands with checkpoints, run the cheap ones.
Report in a few lines: the task, what the handoff says is next, and any divergences found. Material divergence (the plan's premise no longer holds) → surface it and ask before proceeding. Cosmetic drift → note it and continue.
Work rules
- Start with the NEXT section — or the user's explicit steer in the same message ("do step 4") which overrides it.
- "Ruled out — do not reopen" is a hard constraint: do not re-litigate ruled-out hypotheses unless new evidence contradicts the recorded reason.
- Open questions in the file are the user's to answer — ask when one blocks the work.
- Need detail the file lacks? The header's session id allows
claude --resume <id>in another terminal; prefer asking the user before archaeology. - From here on this file is the live handoff of THIS session — /handoff updates it (and marks stages done) as work progresses.
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 · 49 lines · 106 tokens per session scan A 84dc27c3ecfc
pickup is a skill published in the GitHub repository kaisa-kucherenko/claude-code-flow (19 stars, last pushed 11d ago), licensed MIT. It adds 106 tokens to every session and 555 once invoked, about $0.0005 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
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…