OpenClaw Agent Skills is a shared repository of reusable workflows for coding agents working on OpenClaw projects. It provides skills for activities such as code-review closeout, behavior validation, session handoff, remote testing, transcript provenance, and viewing agent sessions. The catalogue entries are the project’s distributed skills and instruction.
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 agentmods add skills/openclaw/agent-skills/handoffnpx skills add openclaw/agent-skills --skill handoffgit clone --depth 1 https://github.com/openclaw/agent-skillsWrote 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/openclaw/agent-skills/handoff)<a href="https://agentmods.dev/skills/openclaw/agent-skills/handoff"><img src="https://agentmods.dev/badge/skills/openclaw/agent-skills/handoff.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 | $0.00018 | $0.00972 |
| Opus 5 | $0.00009 | $0.00486 |
| Sonnet 5 | $0.00004 | $0.00194 |
| Haiku 4.5 | $0.00002 | $0.00097 |
Grade A, and why
handoff 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 5d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- handoff — 94% identical, 13 lines differ
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff
Write a clipboard-ready prompt for another agent to investigate, discuss, or work on a specific task.
Use when the user asks for handoff <task>, "write a handoff", "delegate this",
or wants a prompt for another agent.
Workflow
- Identify the task from the user text. If the user gives only a short label, infer from the current repo, recent discussion, branch name, linked issue/PR, docs, and obvious nearby context.
- Gather enough context to write a useful handoff: repo/product identity, relevant issue/PR/branch names, likely modules, constraints, and known symptoms. Do not perform the receiving agent's full independent review or decide the final technical direction for them.
- Write a standalone prompt for a fresh agent.
- Copy the full prompt to the clipboard.
- Final reply: terse confirmation with the task title. Do not paste the full prompt unless the user asks.
Handoff Prompt Rules
The prompt must:
- Start a discussion, not a command-only work order.
- Ask the receiving agent to do an extensive independent review before changing anything.
- Make clear that the receiving agent owns that review; the handoff only gives starting context and known constraints.
- Ask the agent to decide whether the task is a good idea, stale, already solved, over-scoped, or better handled differently.
- Assume the agent starts in the repo, a parent directory, a workspace directory, or a home directory and can find the repo itself.
- Avoid filesystem paths. No absolute paths, home-directory paths, checkout names, or repo-relative file paths unless the user explicitly requests them.
- Use portable anchors instead: repo owner/name, product/module names, issue/PR URLs, branch names, package/plugin names, public symbols, command names, config keys, exact error text, docs titles, and search terms.
- Include enough context for the receiving agent to get the right repo, boundary, and desired outcome.
- Include constraints, non-goals, validation expectations, and the desired output shape.
- Tell the receiving agent to re-check live repo/GitHub/CI state where relevant.
- Tell the receiving agent not to push, merge, close issues/PRs, label, or post public comments unless the handoff explicitly asks for it.
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.
- 5d ago First seen · 112 lines · 18 tokens per session scan A 1c4ddff7f185
handoff is a skill published in the GitHub repository openclaw/agent-skills (1,078 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 972 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-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…
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…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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.
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…