---
name: ironbee-search-scenario
description: >
  Find reusable IronBee verification scenarios by name, description, or metadata by delegating to
  the ironbee-scenario custom agent. Use when the user types `$ironbee-search-scenario`. The
  sub-agent searches the scenario store and returns the matches.
---

# IronBee — Search scenarios

> **Delegate** — spawn the **`ironbee-scenario` custom agent** via `spawn_agent` with
> `agent_type="ironbee-scenario"` **and `fork_turns="none"`**. The sub-agent owns the scenario tools.

Find saved verification **scenarios**. Read-only.

## Steps
1. **Spawn** `spawn_agent` with `agent_type="ironbee-scenario"` and `fork_turns="none"`, passing in
   `message`:
   > Operation: search
   > Query: \<the user's description — a name/topic for fuzzy search, or a path/tag for metadata match>
   The sub-agent picks the right surface (fuzzy name+description vs precise `metadataMatch`) and searches
   **the scenario store** (one compose store across all platforms). **Wait for the sub-agent in the same turn.** Block on it with `wait_agent` passing `timeout_ms: 600000` (install also sets that as the default wait). A wait that returns with no completed agent is NOT a failure — call `wait_agent` again; do not nudge a still-running agent with `send_message` and do not interrupt it. A run takes minutes.
2. **Relay** the matches — name, description, platform, and (for fuzzy search) relevance score.