dr-fanoutlisted

Fan one deep-research prompt out to several external LLMs at once through a logged-in browser, then collect the reports, archive the originals and synthesize a consensus. Use at the final stage of a research protocol, instead of hand-pasting one prompt into N sites. Triggers: "/dr-fanout", "fan out the DR", "distribute the research prompt".
tonydzi/second-brain-starter-kit · ★ 6 · AI & Automation · score 78

Install: claude install-skill tonydzi/second-brain-starter-kit

# /dr-fanout — fan a Deep Research prompt out to 3+ LLMs and collect a consensus > The final stage of the Alpha Protocol, automated. Channels: **ChatGPT** (chatgpt.com) · **Gemini** (gemini.google.com) · **Grok** (grok.com). The mechanism = the Claude-in-Chrome MCP (the operator's live logged-in Chrome). Canon: [[alpha-protocol-recall-plus-dr]], decision-multi-llm-vendor-independence (heterogeneous consensus), [[chrome-autonomy-self-drive]], [[browser-work-on-peers-not-hub]] (strictly local). ## ⭐ What is already decided (the foundation, don't re-research) — updated 2026-07-16 1. **The browser layer = Firefox-first** (Decision Memo `02-Decisions/decision-2026-07-16-browser-automation-layer.md`, DR26-07-16-HUB-01, confidence high). Chrome 127+ encrypts cookies (ABE) and since April 2026 binds sessions to the hardware (DBSC) → external cookie extraction is impossible without malware techniques. **Firefox cookies are open** (plaintext SQLite, DBSC not implemented) → a dedicated per-service Firefox profile + Playwright `launch_persistent_context`; a Chrome CDP attach is only a fallback for strictly-Chromium sites. The hub stack is already up: `firefox_cookies.py` (`~/.claude/scripts/_shared/`), profiles in `<AUTOMATION_BROWSERS_ROOT>\Firefox\`. 2. **The live Chrome MCP (Claude-in-Chrome) remains the deliberate anti-ban path** for actions that must look like "a human in a real session" (fb-post/x-post go that way). For dr-fanout the choice of execution path (live Chrome MCP vs h