# OrchID Agent Manifest

**Last updated**: 2026-05-30
**Total agents**: 11 (9 OrchID-required + 2 subagent extras)

## OrchID Pipeline Agents (Required)

| Agent | Role | Used By Phases | Source | Model Hint |
|-------|------|---------------|--------|------------|
| scout | Fast codebase recon — returns compressed context for handoff | investigate | references + subagents | inherit |
| researcher | Autonomous web researcher — searches, evaluates, synthesizes brief | investigate | references + subagents | inherit |
| planner | Creates implementation plans from context and requirements | decompose | subagents | inherit |
| worker | Implementation agent for normal tasks and approved oracle handoffs | launch, cleanup | subagents | inherit |
| dev-1 | Focused implementation agent for coding and technical execution | launch | references | deepseek-v4-flash |
| reviewer | Versatile review specialist for code diffs, plans, health, PR validation | converge | references + subagents | inherit |
| tester | Testing and validation — runs tests, verifies fixes, reports regressions | converge | references | deepseek-v4-flash |
| brain | Strategic orchestration and architectural reasoning | any (escalation) | references | glm-5.1-claude |
| delegate | Lightweight subagent that inherits parent model, no default reads | any (simple tasks) | subagents | inherit |

## Additional Agents (from pi-subagents)

| Agent | Role | Notes |
|-------|------|-------|
| context-builder | Analyzes requirements and codebase, generates context and meta-prompt | Used by chain execution |
| oracle | High-context decision-consistency oracle — protects inherited state, prevents drift | Used for validation gates |

## Agent Discovery

Agents are discovered by the pi-subagents extension from the `agents/` directory. Each `.md` file must have valid YAML frontmatter with at minimum a `name` field.

## Model Policy

OrchID does NOT hardcode models. Agent definitions may include `model` hints, but the orchestrator can override them. Default behavior is to inherit the orchestrator's model unless:
1. The user specifies a model explicitly
2. The agent definition declares a specific model preference
3. Cost optimization is requested and the user chooses which model to use

## Adding New Agents

1. Create `agents/<name>.md` with YAML frontmatter (see existing files for format)
2. Add entry to this manifest
3. Run orchID-doctor to verify the new agent is discoverable