Template
Agentic competitive research threat card
Every door a web-browsing research agent can be pushed through, the control that closes it, and the kill switches to test before the first run. No control, no launch.
Fill one card per agent. If a row has no control, the agent does not run. Write NONE and stop. Do not write “the prompt tells it not to.”
Test every kill switch before launch. A cap that has never fired is a cap nobody tested.
Drawing diagram…
Is an agent the right shape?
If you can name the pages, use a scheduled fetch, a diff, and one model step instead. An agent is for open questions where the path is not known.
Toolset (three tools, no more)
| Tool | Allowed | Limit written here |
|---|---|---|
| Search public web | Yes | Queries per run: ____ |
| Fetch page (GET only) | Yes | Pages per run: ____ Bytes per page: ____ |
| Write note to notes store | Yes | One store, append only, schema-validated |
| Send email or post to chat | No | Delivery is a separate approved step |
| Run code or shell | No | Not needed |
| Access the customer relationship management (CRM) system, billing, or files | No | No credentials in the agent environment |
Budgets enforced by the runner
Doors and controls
| Door | Control (write it) | Tested on |
|---|---|---|
| Injected instructions in a page | Date | |
| Scope creep (logins, forms, private areas) | Date | |
| Fabricated findings | Date | |
| Runaway cost or loop | Date | |
| Leaky context in queries or URLs | Date | |
| Quiet drift after a prompt or model change | Date |
Output gate
Kill switches (test each one)
Change control
Need help applying this on a live site? Talk to Simeon Creatives or browse start a conversation.