The customer's coding standards are a hook, not a branch in your prompt

You sell a coding agent to forty engineering teams. Acme wants every file run through their prettier config before it lands. Globex wants a secret scan on every write. Your system prompt grows a paragraph per customer.

Each customer's agent runs in their own container, and hooks are a property of that agent, not of your prompt. Acme's container gets one hook: event PreToolUse, matcher Write|Edit, command npx prettier --write "$HOODY_FILE_PATH", timeout 15 seconds. Writing one is a handshake: POST /api/v1/agent/hooks/begin-write mints a single-use nonce bound to the session and operation, then PUT /api/v1/agent/hooks carries it: and there is a trust acknowledgment before hooks are allowed to fire, because they run shell.

The prompt is the same for everyone. The rules are commands that fire in the customer's box.

Customization moved out of the prompt and into the machine the prompt runs on.