Partner Run Sheet: one page per client when you resell agent work

What you end up with

Every client has one page both teams agree on, and a signature that goes stale the moment that page changes.

What you get

• The method: write who runs it, who owns what and how it stops, per client, before something breaks
• partner.py: 5 file checks and 7 findings (client not told, account not in the client's name, operator approving its own changes, thin support, no data limits, no off switch, no exit plan)
• One run sheet per client and a partner checklist with the open items counted
• Sign-off refused inside an agent session, from anyone but the agency owner, while items are open, or after that client's entry changed
• AGENTS.md, CLAUDE.md, a Grok Bot standing order and a Hermes skill, a fictional example, and 29 tests

Who it is for

Agencies and operators who sell agent work under one brand and run it with another team.

Works with

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

Tools needed

Cost to run: Free. Python is free.
Time to result: First run sheet in about 15 minutes

How it works

1. Run the example

   Unpack the file and run python3 partner.py check example/partners.json.

   Expected: The bakery is ready to sign; the auto glass shop has 7 open items.

2. Fill one real client

   Copy templates/partners.json and fill one client from your agreement, account list and support plan.

   Expected: partner.py check lists that client's open items.

3. Sheets and fixes

   Run sheets, then draft a fix for each open item and take it to the client.

   Expected: One run sheet per client and checklist.md.

4. Sign at your own terminal

   When a client has no open items, the agency owner runs approve for that client.

   Expected: status shows signed, and CHANGED if the entry is edited later.

Sample prompts, free to use

Follow AGENTS.md. Run partner.py status, then sheets for any client with open items, and send the agency owner each run sheet with a drafted fix per item. Do not sign, edit signed.json, move an account or contact the client or the operator.

Free preview of the file

# Partner Run Sheet

**Reselling agent work under your own brand? Keep one page per client that says who runs it, who owns every account, who approves changes, and what the client keeps if the partner arrangement ends.**

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

An agency sells the work. Another team runs the agents. The client sees one brand. That setup is common and it can be fine, until something breaks at night and nobody knows who answers, or the arrangement ends and the client finds out their phone number belongs to a company they never signed with.

Most of that trouble is decided in advance by a few written answers. This kit makes you write them per client and will not let the page be signed while one is missing.

## What you get out of it

- One run sheet per client: brand shown, who operates, desks and approvers, accounts and owners, support, escalation, data limits, off switch, exit.
- A partner checklist across every client with the open items counted.
- A signature from the agency owner on each clean sheet, which goes stale on its own if that client's entry changes.

## Who it is for

Agencies and consultants who resell or white-label agent work run by a partner, and operators who run agents behind someone else's brand and want the same page on both sides.

Not a contract and not legal advice. It records what your agreement says and poin

Worth knowing

• It checks what is written, not what is true. A disclosure sentence the client never saw passes the check.
• One agency and one operator per file.
• On 2026-11-03: 29 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 a contract and not legal advice.

Details

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

Related

Prompt packFree

Clean Handover: keep running if your agent provider stops tomorrow

by PaperChaseWebb

A free kit for anyone who pays for agent or automation work, and for the providers who do it. List every account, data store, automation, schedule and bill the work touches in one register. A checker finds each place the client would be stranded: an account in the provider's name, no client admin, an export never tested, a job with no runbook or off switch, a bill the provider pays. Then it turns every gap into one decision sheet the client owner answers in a single reply.

Works withClaude CodeCodexGrok BotHermesOne Python script, a register template, a fictional bakery example with a runbook, and agent rules for each harness. Tested on Linux

Solo business · Beginner · 15 min 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 pack$29

Desk Authority Map: who in your agent fleet may decide what

by PaperChaseWebb

Four plain files say, for every desk and action, decide, propose, ask-owner or never, with dollar limits, escalation and the evidence each desk owes. Agents ask authority.py before they act and get the answer as an exit code; anything not in the map is never. Owner yeses are typed at the owner's terminal, tied to one request's sha256, good for one use, and refused inside an agent. Fifteen read-only checks run on the map itself.

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 · 30 min setup

Prompt packFree

Usage Cap Check: see the month coming before the agent bill does

by PaperChaseWebb

A free kit for providers who bill agent or model usage to clients, and for the owners who pay it. Write one plan with a monthly cap, alert points, a rule for going over and every job that spends. Copy usage from the provider's own export into a three-column log. A checker gives spend to date, the last 7 days' pace and where the month lands, flags jobs over budget, unplanned spend and jobs with no off switch, and turns each into one decision sheet the client owner answers in a single reply.

Works withClaude CodeCodexGrok BotHermesOne Python script, a plan and log template, a fictional plumbing company example, and agent rules for each harness. Tested on Linux

Solo business · Beginner · 15 min setup