Agents
13 specialized agents that each carry encoded expertise — Scout, Synthesizer, Writer, Analyst, Planner, Builder, Judge, Emissary, and more. Split the work. Run it in parallel. Each agent knows exactly what to do.
The problem
One conversation, one task, one thread. You can’t run research while writing while analyzing. Every task gets your full attention or none of it.
Agent Prime splits the work across specialized agents that each carry encoded expertise. Scout doesn’t write. Writer doesn’t analyze markets. Prime doesn’t do the work — it routes it. Specialization is how you scale output without scaling effort.
The 13 agents
Each agent carries structured identity metadata — an emoji, a color, and a “vibe” that captures how it thinks and talks. These aren’t decorative. Each agent’s prompt includes 5 example phrases that shape its editorial judgment through implicit few-shot learning.
Agent anatomy
Every agent is a markdown file with a five-layer sandwich structure. LLMs weight early and late content more heavily — hard rules at both ends means compliance is structurally enforced.
┌─────────────────────────────────────────┐ │ IDENTITY FRONTMATTER (YAML) │ name, color, emoji, vibe ├─────────────────────────────────────────┤ │ CONTEXT VERIFICATION GATE │ must load files before output ├─────────────────────────────────────────┤ │ IDENTITY + CORE DIRECTIVE │ who am I, what do I optimize ├─────────────────────────────────────────┤ │ METHODOLOGY │ step-by-step with decision gates ├─────────────────────────────────────────┤ │ QUALITY CHECKLIST + COMM STYLE │ self-check + 5 example phrases └─────────────────────────────────────────┘
Handoff protocol
Agent-to-agent transfers use 5 standardized templates. Every transfer uses a template. Artifacts must have paths. Escalations go to Prime.
Real example
Every agent prompt starts with YAML frontmatter that encodes its identity, followed by a Context Verification Gate. Here’s how Scout’s prompt opens:
---
name: Scout
emoji: 🔍
color: "#4A90D9"
vibe: "Finds the 10 signals that matter from the
1,000 that don't — then proves every one"
---
## Context Verification Gate
Before producing ANY output, verify access to:
- [ ] shared/context.md (identity + epistemic guardrails)
- [ ] shared/learnings.md (accumulated corrections)
- [ ] shared/registry.json (current work items)
- [ ] agents/scout/signals/ (prior signal scans)
If ANY file is missing, STOP and ask.
The gate is non-negotiable. A 200-word output requires the same gate as a 4,000-word analysis. The identity frontmatter makes agents instantly recognizable in logs and multi-agent pipelines.
How to set it up
Each agent is a standalone markdown file. Start with one — Scout for research, Writer for content, Planner for breaking down projects. Use the five-layer structure:
--- name: Your Agent emoji: 🛠 vibe: "One sentence that captures how it thinks" --- ## Context Verification Gate Verify required files before producing anything ## Identity + Core Directive What this agent does and optimizes for ## Methodology Step-by-step process, sequential not summarizable ## Quality Checklist + Communication Style Self-check + 5 example phrases for voice
The communication style section at the bottom provides implicit few-shot learning — 5 example phrases that shape how the agent talks and makes judgment calls. These compound: Scout signals feed Synthesizer theses, which feed Writer drafts, which Connector distributes.