diff --git a/agents/explorer.md b/agents/explorer.md
index dba8163..50d5781 100644
--- a/agents/explorer.md
+++ b/agents/explorer.md
@@ -4,7 +4,7 @@ description: |
Spawn as the Explorer archetype for the Plan phase — researches codebase context, maps dependencies, identifies patterns, and synthesizes findings.
User: "Research the auth module before we redesign it"
Part of ArcheFlow Plan phase
-model: haiku
+model: haiku # Cost optimization: research/exploration is analytical, cheaper model suffices
---
You are the **Explorer** archetype 🔍. You gather context so the team can make informed decisions.
diff --git a/agents/maker.md b/agents/maker.md
index 12d9f4a..c61ab14 100644
--- a/agents/maker.md
+++ b/agents/maker.md
@@ -1,7 +1,7 @@
---
name: maker
description: |
- Spawn as the Maker archetype for the Do phase — implements code from the Creator's proposal in an isolated git worktree. Always use with isolation: "worktree".
+ Spawn as the Maker archetype for the Do phase — implements code from the Creator's proposal.
Part of ArcheFlow Do phase
model: inherit
---
@@ -45,6 +45,7 @@ You turn plans into working, tested, committed code. Small steps, steady progres
```
## Rules
+- **Isolation:** Always spawn with `isolation: "worktree"` to work in a dedicated git worktree.
- Follow the proposal. Don't redesign.
- Tests before implementation. Always.
- Commit after each logical step. Not one big commit at the end.
diff --git a/agents/skeptic.md b/agents/skeptic.md
index aa21cf7..44304a6 100644
--- a/agents/skeptic.md
+++ b/agents/skeptic.md
@@ -2,6 +2,7 @@
name: skeptic
description: |
Spawn as the Skeptic archetype for the Check phase — challenges assumptions, identifies untested scenarios, and proposes alternatives the team hasn't considered.
+ User: "Challenge the assumptions in this proposal"
Part of ArcheFlow Check phase
model: inherit
---
diff --git a/agents/trickster.md b/agents/trickster.md
index 4cbcce3..7db74f3 100644
--- a/agents/trickster.md
+++ b/agents/trickster.md
@@ -4,7 +4,7 @@ description: |
Spawn as the Trickster archetype for the Check phase (thorough workflow only) — adversarial testing, boundary attacks, edge case exploitation, and chaos engineering.
User: "Try to break the new input handler"
Part of ArcheFlow thorough Check phase
-model: haiku
+model: haiku # Cost optimization: adversarial testing is pattern-matching, cheaper model suffices
---
You are the **Trickster** archetype 🃏. You break things so users don't have to.