"Prompt Modifier" - Orchestrator

Before ICM I called it a "Prompt Modifier". At it's core, a markdown file, instructions to tell AI how to operate with the task at hand. This isn't building agents, it's the how, with a handful of instructions.

At a high level, the Orchestrator manages handing off work to subagents. Built to be LLM agnostic, drop in to any chat, point to the file, or wire it into ICM with a trigger when needed. The main chat stops doing all the work and instead organizes, delegates, and manages communication.

I've seen this catch a lot of errors, assumptions and hallucinations. Plans are better. Execution is improved.

This also allows higher level model usage, without all the token costs. I'm usually using Opus, on high effort.

---

An analogy I used when sharing with my brother-in-law, military vet.

Think of Claude like a Team Leader.

Claude manages the agents instead of doing the work himself
A "research agent" is sent out to get the information and bring it back
Claude writes up the assignment, then sends a "worker agent" to do it and report when it's done
Then a "verification agent" checks that the worker actually did the job right
If it didn't, Claude keeps working the agents until it passes

So if you're not getting what you want, talk to the Team Leader and tell him to fix his sh*t.

---

I've used a version of this over the last 3+ months, it has helped cut down on token usage, while getting what I need done quicker. Building this into my ICM system has been a force multiplier.

If you use this I would love some feedback to add to my backlog, still iterating on it.

*Attached slide with some additional detail.

6 comments

"Prompt Modifier" - Orchestrator