build-omnigentlisted

# Agent Generation Use these patterns to generate a valid agent directory. Always generate the minimal set of files needed — don't over-engineer. Every template below has been validated with the same parser/validator that `omnigent server` uses. If your environment exposes the `validate_agent` tool (the dedicated agent-authoring environment does), run it after generating files to confirm the spec loads. Load the **`omnigent-knowledge`** skill if you need the deeper field reference (executor types, os_env, guardrails, sandboxing). ## Step 1: Choose a directory name Use the agent name in kebab-case: `my-research-agent/` ## Step 2: Generate config.yaml Always include: - `spec_version: 1` - `name` (lowercase, hyphens OK) - `description` (one sentence) - `instructions` — path to a file (default `AGENTS.md`) or inline text. (`prompt:` is an accepted alias; `instructions:` wins if both are set.) - `executor` — how the agent runs. See Step 2a. Include if needed: - `tools.builtins` — built-in tools. The current set is `download_file`, `export_agent`, `list_files`, `search_conversations`, `upload_file`, `web_fetch`, `web_search`. If the `list_builtin_tools` tool is available, call it for the authoritative live set rather than trusting this list. - `tools.agents` — sub-agents (must match `agents/` subdirectories). - `os_env` — filesystem/shell access for harness agents (see the shell-capable template). - `interaction.modalities` — if the agent handles images or files. -