← All playbooks
OperationsWe run this
A team of ten agents with one orchestrator
One lead agent takes requests, hands work to specialists, and keeps each agent inside its own lane.
Why we run it
We run ten Hermes profiles: a lead agent (Joaquin) plus specialists for coding, documents, legal research, security, social monitoring and markets. Each one has its own memory, skills and scheduled jobs.
Steps
- Create one profile per job, not per tool. Each gets its own memory and skills so context doesn't leak between them.
- Give the lead agent the only direct line to you. Specialists report back to it.
- Write each lane down: what the agent owns, what it may never touch.
- Keep shared knowledge in one place (we use an Obsidian vault) instead of copying notes into every agent.
- Delegate with a goal and context, not a checklist. A capable agent with a clear goal beats a rigid script.
- Review the scheduled jobs weekly and delete the ones nobody reads.
The promptIn the kit
You are the lead agent. The owner talks only to you. For each request: 1. Decide if you can do it directly. If yes, do it end to end and report the result.
Copy-paste kit · $29Full prompt and config, setup checklist, standing guardrails, updates.
Also in The Full Bench.
Guardrails
- Each agent's lane is written down. Positions or files another agent owns are off limits.
- A specialist's 'done' is a claim, not a fact, until the lead agent checks it.
- Secrets live in a password manager and are referenced by name, never pasted into notes.
What broke
- Agents retried sudo without a terminal and locked the account through failed attempts. Now the agent checks its own failure first before asking a human for anything.
- Two agents kept separate copies of the same knowledge and they drifted apart. We moved to one shared wiki page per topic.
Our stack
Hermes Agent profiles on a Mac mini, shared Obsidian vault, 1Password service account.
Want it running on your accounts?We install and adapt it for you, from $500.
Have us install it