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

What you end up with

A new agent that starts from short, dated, owner-approved briefings and a limits card, with no secrets and no old approvals carried over.

What you get

• The intake method: plan in three tiers (pull first, desk card, never pull), ask, check, approve, build
• intake.py: 10 packet checks, 5 limits card checks and 5 plan checks, with secrets shown masked, never printed
• A seven-section packet template and a limits card template with the required lines
• Owner sign-off that is refused inside an agent session, and a build that refuses any file changed after sign-off
• AGENTS.md, CLAUDE.md, a Grok Bot standing order and a Hermes skill, a fictional four-source example, and 31 tests

Who it is for

Anyone adding an agent to a fleet who wants it briefed from the others without secrets, stale facts or old approvals.

Works with

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

Tools needed

Cost to run: Free. Python is free.
Time to result: First checked intake in about an hour

How it works

1. Run the example

   Unpack the file and run python3 intake.py check example/plan.json --today 2026-11-03.

   Expected: intake OK: 0 errors.

2. Plan the intake

   List the agents that know something in plan.json and give each a tier. Anything with logins, money or personal details is tier 3.

   Expected: check shows no T codes.

3. Collect and check

   Send each source the request from intake.py ask, save the replies under packets/, and run check until it is clean.

   Expected: 0 errors; warnings read and handled.

4. Approve and build

   Run intake.py approve yourself, then build. Give the new agent context/standing-context.md.

   Expected: Standing context with the limits card first and no tier 3 content.

Sample prompts, free to use

Follow AGENTS.md. For each tier 1 and tier 2 source in plan.json, run intake.py ask and send that request to the source only. Save the replies under packets/, run intake.py check, and tell me in two lines what is ready. Do not run approve.

Free preview of the file

# Agent Intake Packet

**Brief a new agent from the agents you already run: short, dated packets, a limits card, and your sign-off before it reads a word. No secrets cross over.**

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

A new agent starts cold. The quick fix is to paste it everything: old chats, notes, a folder of files. That is how a key ends up in a prompt, a private detail ends up in a draft, and a decision from last month gets treated as a decision for today. Or the new agent reads an old "yes" and acts on it.

This kit replaces the paste with a short intake. Every agent that knows something writes one page in the same shape. A checker stops secrets, stale pages and raw dumps. You sign off. Only then does the new agent get its standing context, with the limits card on top.

## Who it is for

Owners and operators running two or more agents (a chief of staff, desks for booking, content, support or books) who are adding another one, or moving an agent to a new role. Also useful when you switch harnesses and want the new one to start from the same facts.

Not a memory system and not a permissions system. It produces one reviewed briefing. Your tools still decide what each agent can reach.

## How it works

1. **Plan (10 minutes).** List every source agent in plan.json and give each a tier.

| Tier | Means | What happens |
| --- | --- | --- |
| 1 | 

Worth knowing

• The secret patterns catch common key and password shapes, not every possible secret. Read the packets before you approve.
• It checks that the limits card says the right things. Your tools and your yes enforce them.
• On 2026-11-03: 31 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.

Details

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

Related

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

Pilot Scorecard: agree the pass line before an agent pilot starts

by PaperChaseWebb

A free kit for providers who offer a trial before a monthly plan, and for owners who want to try one. Write one page of terms: one workflow, 30 days at most, up to 5 measures with today's number, a target and where each number comes from, plus data limits, an off switch, the refund rule and the next step after a pass or a fail. The client owner signs it at their own terminal, the pass lines lock, and the end report says pass or fail per measure without an argument.

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

Solo business · Beginner · 15 min setup

Bot template$39

Cross-Harness Relay: seats, handoffs and a tested Agent Run Record for Grok Bot, Claude Code, Codex and Hermes

by PaperChaseWebb

A bot template and teaching guide for running more than one agent harness on the same work: six seat cards, a RELAY.md seat map, a relay packet for every handoff, four loop shapes, routine-or-judgment routing with a fallback, a preflight check, the front desk and night shift split with a proof footer, shared memory rules, relay drills, a rules block and prompts. v1.1 adds the Agent Run Record (the owner's ask, every step, what broke and what fixed it, the diff and each changed file with its sha256), a local redaction check for keys, tokens, emails, phone numbers and private paths before a record is shared, a rule that exactly one named seat may deploy, share and deploy approvals the owner types at their own terminal, tied to hashes and refused inside an agent or with piped input, a run record folder with a fifteen-check read-only checker and a relay helper, agent files for Grok Bot, Claude Code, Codex and Hermes, three new relay drills (eleven in all) and six new prompts (20 in all). Price unchanged.

Works withClaude CodeCodexGrok BotHermesPlain .md plus two Python 3 scripts, standard library only. A 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, and the toolkit was not run on a real multi-harness job

Vibe coding · Intermediate · 1 hr 30 min setup

Prompt pack$39

Grok Bot Templates: personas, standing orders and handoffs

by PaperChaseWebb

A Markdown pack plus a small checker for setting up Grok Bots that do useful work on a schedule: 8 ready-to-paste personas, standing order cards, event routine recipes, multi-bot handoffs with a decision log, an approvals log and six approval gates, memory rules, a test set, and bot_check.py to check your setup.

Works withClaude CodeCodexGrok BotHermesPlain .md; the optional checker needs Python 3.8 or newer

Solo business · Beginner · 15 min setup