grimdevthree-minions-in-a-trench-coat

Solid

Three Minions in a Trench Coat: manual-only multi-model coding council that runs three top Minion routes in parallel, compares their answers, and synthesizes the best final answer.

AI & Automation 19 stars 0 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
43
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
59
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Three Minions in a Trench Coat Three minions in a trench coat is a multi-model coding council Imagine sneaking into a theater stacked in a trench coat, combined with sitting in front of a whiteboard brainstorming solutions & talking, or a smaller inner circle of friends late at night around the campfire. Three minions is designed to runs multiple subagents together Model Choice: - Prefer diversity across providers over three near-duplicates from one provider ## Trench Coat Wrapper If current harness has a subagent tool, first create 1 subagent trench coat wrapper with a medium tier model, in watcher and orchestrator mode, this subagent will then spawn the 3 subagents and manage them and report results back. The goal is to avoid bothering the root agent with smaller details and problems and wasting tokens on details that can be resolved. As things finish, be sure to pass it back to the parent agent with full handoffs of all crucial information, so the parent agent can review & incorporate all progress and decisions made. ## Relationship To Minion Use `grim:dev:minion` for subagent protocol, always read this to ensure proper usage of three minions.

Details

Author
MindGoblinStudios
Repository
MindGoblinStudios/grim-tome
Created
2 weeks ago
Last Updated
yesterday
Language
JavaScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

grimdevminion

Minion: manual-only routing note for using built-in subagents first, or direct Codex, Claude, Cursor, Grok, LM Studio, Ollama, and OpenRouter runners when explicitly requested.

19 Updated yesterday
MindGoblinStudios
AI & Automation Listed

bearing-minions

Fan work out to a swarm of cheap, anchored subagents that GATHER — for wide mechanical work you would otherwise grind through serially: finding every call site, auditing N files against one rule, discovering migration sites, cross-referencing a list against the codebase, 'where is this used and how does it flow'. Use when the work is bounded, verifiable, independent and wide (3+ units). NOT when the judgment IS the work, when the answer only survives verbatim, or when the unit needs conversation context the minion was never in. Examples: "find every place we do X", "which files still use the old API", "trace all callers of these 12 symbols", "audit every route for auth".

6 Updated yesterday
ReidenXerx
AI & Automation Listed

send-to-minion

Use this skill only when the user explicitly invokes $send-to-minion, /send-to-minion, or explicitly asks to delegate a prompt to one minion, helper, worker, child agent, spawned agent, subagent, Claude Code agent, or other single delegated agent. It sends the user's prompt to exactly one subagent using the current runtime's delegation tools, coordinates follow-up with the runtime's messaging/resume tools, verifies the result, and returns the parent agent's final answer.

7 Updated 1 months ago
bastos