Clean Handover: keep running if your agent provider stops tomorrow

What you end up with

A client who could keep running tomorrow, and a dated plan of only the handover steps they approved.

What you get

• The method: one register, one test (could the client keep running tomorrow?), one reply, one plan with done tests
• handover.py: 4 register checks, 6 gap checks and 4 reply checks across accounts, data, automations, schedules and bills
• A one-reply decision sheet with options for every gap, including an honest accept that is dated and signed in the plan
• Owner decisions refused inside an agent session, from anyone but the client owner, or after the register or a runbook changes
• AGENTS.md, CLAUDE.md, a Grok Bot standing order and a Hermes skill, a fictional example, and 28 tests

Who it is for

Owners who want proof they are not locked in, and providers who want to hand every client a clean exit.

Works with

Solid chips: the agent is named in this listing's own tools list. Dashed chip: One Python script, a register template, a fictional bakery example with a runbook, and agent rules for each harness. Tested on Linux.

Tools needed

Cost to run: Free. Python is free.
Time to result: First scan in about 20 minutes

How it works

1. Run the example

   Unpack the file and run python3 handover.py scan example/handover.json --today 2026-11-03.

   Expected: 9 gaps across 6 systems; the order inbox agent is clean.

2. List your systems

   Fill in templates/handover.json with every account, data store, automation, schedule and bill, and write a runbook for each job.

   Expected: handover.py check shows 0 errors.

3. Scan and send

   Run scan, then sheet, and send decisions.md to the client owner.

   Expected: decisions.md with one numbered item per gap.

4. Reply once, then plan

   The client owner answers in one line at their own terminal, then run plan and work each step with the client watching.

   Expected: handover-plan.md with only the approved steps, each with a done test.

Sample prompts, free to use

Follow AGENTS.md. Ask what changed, draft updates to handover.json and runbooks/ for review, run handover.py scan, and if there are gaps, run sheet and send the client owner decisions.md with the reply line. Do not sign in anywhere, move an account or write a secret into the folder.

Free preview of the file

# Clean Handover

**If your provider stopped tomorrow, could you keep running? One register of every account, export, automation and bill the work touches, a checker that finds each place the answer is no, and one reply to close the gaps.**

Version 1.0, 2026-11-03. By PaperChaseWebb Inc. Free. Works with Grok Bot, Claude Code, Codex and Hermes, or by hand. Python 3.8 or newer, no installs.

## The problem

Agent and automation work piles up quietly. A host signed up on the provider's card. A customer list the client cannot export. A weekly job nobody on the client side knows how to pause. None of it matters until the contract ends, the provider is unreachable, or something breaks at 6 AM. Then it is the only thing that matters.

A good provider wants this list as much as the client does. It is the clearest proof that the client stays because the work is good, not because leaving is hard.

## What you get out of it

- One register of every system the work touches, with who owns it, who can administer it, how to export it, how to switch it off and who answers for it.
- A scan that names every gap by system, in plain words.
- One decision sheet with a numbered item per gap and a reply line like `1: test 2: transfer 3: accept`. Answer in one message.
- A handover plan of only the steps the client approved, each with a done test the client checks themselves.

## Who it is for

Owners who pay for agent or automation work and want to know they are not locked in. Providers and small

Worth knowing

• It knows only what the register lists. Walk it with both sides before you trust the scan.
• It checks that a runbook file exists, not that it is good, and it never signs in, so people confirm each done test.
• On 2026-11-03: 28 tests passed on Python 3.8, 3.9, 3.11, 3.12 and 3.13 on Linux, run from the files unpacked out of the pack. Agent rules guide; they were not loaded inside each harness for this release.
• Not legal advice, and not a substitute for the exit terms in a contract.

Details

Version 1.0 · Updated Nov 3, 2026 · Markdown version of this page
License: Personal and commercial use. Download terms

Related

Prompt pack$19

Reach Inventory: every connector your agents hold, with a job, an owner and a way out

by PaperChaseWebb

One row for every connector, MCP server, OAuth grant, API key and automation bridge your agents can use, each tied to a job and marked necessary, convenient or leftover. Scope granted is set against the scope the job needs, keys are named by where they live and never pasted, bridges list every app behind them, and leftover access is removed with a date and proof. Agents list and propose; removals, narrower scopes, rotations and new grants wait for your yes at your own terminal, tied to the sha256 of the inventory. Fifteen read-only checks run on the inventory.

Works withClaude CodeCodexGrok BotHermesA skill file for Claude Code, Codex and Hermes, an AGENTS.md snippet and a Grok Bot rules block; the scripts were tested on Linux with Python 3.13, the agent files were not loaded inside each harness

Solo business · Intermediate · 1 hr setup

Prompt pack$29

Retainer Scope Sheet: itemize what an agent monthly covers

by PaperChaseWebb

One sheet per client that says line by line what your monthly agent retainer covers: the desks it runs and how many runs each, included hours and what happens over the limit, response times with covered hours, what is not included, what needs the client's yes, the reports they get and how changes are asked for. A checker fails every vague line ("ongoing support", "as needed", "ASAP"), an overage with no rate, a desk that sends or books with no yes row, and checks your proposals, change requests and invoices against the sheet. You approve each sheet at your own terminal.

Works withClaude CodeCodexGrok BotHermesPlain Markdown files, a small Python checker, and rules for AGENTS.md and CLAUDE.md, Claude Code and Codex notes, Hermes notes and a Grok Bot standing order. The agent files were checked by the checker on Linux; they were not loaded inside each agent for this release

Solo business · Intermediate · 30 min setup

Prompt packFree

Agent Intake Packet: brief a new agent without handing over secrets

by PaperChaseWebb

A free kit for adding an agent to the ones you already run. Every agent that knows something writes one dated page in the same seven sections. A checker stops keys, passwords, stale pages, pasted chat logs and topics you never share. You sign off at your own terminal, and only then does the new agent get its standing context, with a limits card on top.

Works withClaude CodeCodexGrok BotHermesOne Python script, templates, a fictional example and agent rules for each harness. Tested on Linux

Solo business · Intermediate · 15 min setup