padosoft-agent-host-boundarieslisted

Use this skill when building or reviewing something that calls a model or hosts an agent — an LLM adapter, a tool-calling loop, an MCP server, a prompt-driven feature, a spend budget, a trajectory or replay store, a similarity or scoring threshold, an agent-generated artifact that a human is meant to approve. Also when the user reports a runaway bill, prompts or customer data ending up in logs or traces, an agent doing more than intended, a "confidence score" being treated as a decision, or generated output being accepted as evidence. Do not use it for prompt wording and model choice, for training or fine-tuning, or for building the skills themselves (padosoft-skill-creator covers that).
padosoft/skills · ★ 1 · AI & Automation · score 80

Install: claude install-skill padosoft/skills

# Agent and LLM host boundaries The model is a provider. The agent is a caller with unusual reach. Everything below is a boundary the **host** owns — and every one of them has a failure mode where the system looks like it is working. **The rule: the host decides what is allowed, what is recorded, and what any of it is allowed to prove.** --- ## 1. An adapter is not production-grade because it parses a 200 The minimum contract for a call that leaves the process: | Control | Why | |---|---| | Abortable timeout | otherwise one hung call holds a worker until something else times out | | Maximum generation bound | an unbounded response is an unbounded bill and an unbounded payload | | Injectable transport | deterministic tests without a network, and without pretending the network was tested | | Redacted prompt, response **and error** | the error path is the one that leaks, because nobody redacts it | | Model provenance hash | so a recorded result can be attributed to a specific model identity | **One wire protocol does not cover every vendor.** Roles, content blocks, tool schema names and usage fields differ; registering two providers behind one "compatible" adapter makes the tests green while sending semantically wrong requests. Each provider gets its own bounded adapter, and an unsupported one stays explicitly unsupported rather than silently falling back. ## 2. Budgets are enforced twice, and their exhaustion is an event ```text before dispatch → estimate, and refuse a