Multi-model review and analysis — agents for Claude (codex-solver, gemini-solver, oracle-solver, counsel-reviewer) and skills for Codex (claude-solver, gemini-solver, oracle-solver, counsel-reviewer) with confidence scoring, security auditing, and CLI permission hooks
npx claudepluginhub shravansunder/ai-tools --plugin quorum-counselUse this agent as a BACKGROUND task (run_in_background:true is REQUIRED) when stuck on problems, need deep codebase exploration, or architecture design. Delegates to OpenAI Codex via the codex CLI. Codex excels at autonomous multi-file analysis, backend architecture reasoning, and finding issues Claude missed. The agent takes 5-30 minutes - always spawn in background so you can continue helping the user. **CRITICAL - Detailed Context Required**: When calling this agent, provide EXTENSIVE detail: exact file paths, function/class names, line numbers, complete code snippets, error messages, what you've tried, architectural context, constraints, and specific questions. Vague prompts produce poor results. **Key signals to use this agent**: - Claude has tried 2+ approaches without success (stuck debugging) - Need to trace dependencies across many files (codebase exploration) - Need architecture design with trade-off analysis (new component design) - Need impact analysis of a proposed change (what breaks if we change X?) - Want a different perspective on a hard problem (second opinion)
Always use this agent as a BACKGROUND task (run_in_background:true is REQUIRED) for mandatory plan review and code review. Orchestrates both Gemini 3.x and Codex GPT-5.x in parallel, then synthesizes findings into a unified review with consensus issues and model-specific insights. **CRITICAL**: Caller must provide a complete Context Bundle (requirements, plan/background, constraints, artifacts, review questions). If missing, the reviewer proceeds but must emit Context Sufficiency Warnings and reduce confidence. **MANDATORY Use Cases**: 1. **Plan Review**: ALWAYS use after creating implementation plans (validate approach, gaps, edge cases, alternatives) 2. **Code Review**: ALWAYS use after completing implementation (before claiming done) (bugs, security, test gaps, quality) **Do NOT use for**: quick fixes or exploration/debugging (use codex-solver instead).
Use this agent as a BACKGROUND task (run_in_background:true is REQUIRED) when you need a different perspective, large-scale codebase understanding, or architecture analysis. Delegates to Google Gemini via the gemini CLI in read-only mode. Gemini excels at massive context understanding (1M+ tokens), system-wide pattern recognition, and producing clear explanations. The agent takes 2-10 minutes - always spawn in background so you can continue helping the user. **CRITICAL - Detailed Context Required**: When calling this agent, provide EXTENSIVE detail: exact file paths, function/class names, line numbers, complete code snippets, error messages, what you've tried, architectural context, constraints, and specific questions. Vague prompts produce poor results. **Key signals to use this agent**: - Need to understand a large or unfamiliar codebase (massive context window) - Need architecture analysis or system-wide pattern recognition - Want a second opinion from a different model family (Gemini vs Claude/Codex) - Need detailed explanation of complex code or data flows - Need to trace cross-cutting concerns across many files
**NEVER invoke automatically — only when the user EXPLICITLY asks.** Use this agent as a BACKGROUND task (run_in_background:true is REQUIRED) to consult GPT-5.4 Pro via browser automation. Oracle is a heavy hitter: expensive (ChatGPT Pro subscription), slow (10-30 minutes per run), and must be loaded with maximum context. Delegates to the `pnpx @steipete/oracle` CLI in browser mode. **CRITICAL — User-Initiated Only**: Do NOT spawn this agent proactively, from hooks, or from review gates. The user must explicitly ask to consult Oracle. This is non-negotiable. **CRITICAL — Maximum Context Required**: Oracle starts empty — it cannot read your codebase. You MUST bundle ALL relevant files via `--file` flags, include a full project briefing in the prompt, and provide detailed questions. Skimpy prompts produce useless results. **Key signals (only when user asks)**: - User says "ask Oracle", "consult Oracle", "run Oracle", or similar - Need GPT-5.4 Pro's perspective on a hard problem - Want a thorough second opinion with deep reasoning - Complex analysis that benefits from Pro-level thinking time
Claude Code plugins and sandboxed Docker environments for AI coding assistants.
Install via the Claude Code marketplace:
/plugin marketplace add ShravanSunder/ai-tools
Then install individual plugins with /plugin install <name>@ai-tools.
| Plugin | Description |
|---|---|
ai-scaffold | Project scaffolding with standard dev configs (biome, ruff, vitest, pytest, cursor rules, claude hooks) |
skill-peekaboo | Visual UI testing for macOS apps using Peekaboo CLI |
quorum-counsel | Multi-model review orchestration -- counsel-reviewer and codex-solver background agents |
See plugins/ for full details.
Run AI coding agents (Claude Code, Codex, Gemini CLI) inside Docker containers with network-level isolation. The agent gets full workspace access but can only reach domains you explicitly allow.
# From any git repository
run-agent-sidecar.sh --run-claude
AI agents with tool use can execute arbitrary shell commands, install packages, and make network requests. Running them in a container with an egress firewall provides a practical security boundary without giving up functionality:
flowchart LR
subgraph host ["Host Machine"]
ctl["sidecar-ctl.sh\n(firewall control)"]
run["run-agent-sidecar.sh"]
end
subgraph container ["Docker Container"]
fw["iptables + dnsmasq\n(egress firewall)"]
agent["AI Agent\n(claude / codex / gemini)"]
ws["/workspace\n(bind mount)"]
end
run -->|"build + start"| container
ctl -->|"allow / block domains"| fw
agent -->|"read/write files"| ws
agent -->|"network requests"| fw
fw -->|"allowed domains only"| internet["npm, pypi, AI APIs\n(allowlisted)"]
fw -.->|"blocked"| blocked["everything else"]
| Concern | How it's handled |
|---|---|
| Arbitrary network access | Egress firewall blocks all traffic except allowlisted domains (npm, pypi, AI APIs). Toggle presets for GitHub push, Notion, Linear. |
| Persistent state leaking | Named volumes isolate shell history, venvs, node_modules per workspace. Container recreation is cheap (--reload ~5s). |
| Package supply chain | APT repos blocked at firewall level after build. Runtime installs impossible. |
| Git corruption | .git/ mounted read-only. Agent can read history but cannot rewrite refs or force-push. |
| Config tampering | .agent_sidecar/ shadowed with empty tmpfs. Agent cannot read or modify sidecar configuration. |
| Scope creep across repos | Each repo gets its own container, volumes, and firewall rules. No cross-repo contamination. |
Three-tier config hierarchy lets you customize per-team and per-developer without forking:
Base (agent_sidecar/setup/) -- defaults shipped with this repo
+ Repo (.agent_sidecar/*.repo.*) -- team overrides, committed
+ Local (.agent_sidecar/*.local.*) -- personal overrides, gitignored
Additive files (firewall allowlists, zshrc, init scripts) merge all tiers. Override files (config, dockerfile) pick the highest-priority tier.
run-agent-sidecar.sh --run-claude # Start Claude Code in sidecar
run-agent-sidecar.sh --run-codex # Start Codex
run-agent-sidecar.sh --run-gemini # Start Gemini CLI
run-agent-sidecar.sh --reload # Recreate container (~5s)
run-agent-sidecar.sh --full-reset # Rebuild image + recreate (~2-5min)
sidecar-ctl firewall allow notion # Allow Notion API
sidecar-ctl firewall toggle 15m # Enable all presets for 15 minutes
sidecar-ctl firewall clear # Revoke all toggle access
sidecar-ctl status # Show container + firewall state
See agent_sidecar/ for full setup, architecture, and configuration docs.
ai-tools/
├── plugins/ # Claude Code plugins
│ ├── ai-scaffold/ # Project scaffolding
│ ├── skill-peekaboo/ # macOS visual UI testing
│ └── quorum-counsel/ # Multi-model review orchestration
├── skills/ # Pure skills (future)
├── agent_sidecar/ # Docker sidecar system
└── CLAUDE.md # Agent instructions
v9.30.0 — Model defaults refreshed: Opus 4.7 for planning/strategy/security-review, GPT-5.4 for code-review/implementation. New GPT-5.4 prompting guide. Set OCTOPUS_LEGACY_ROLES=1 to opt out. Run /octo:setup.
Uses power tools
Uses Bash, Write, or Edit tools
Battle-tested Claude Code plugin for engineering teams — 48 agents, 184 skills, 79 legacy command shims, production-ready hooks, and selective install workflows evolved through continuous real-world use
Complete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, rules, and legacy command shims evolved over 10+ months of intensive daily use
Complete collection of battle-tested Claude Code configs agents, skills, hooks, rules, and legacy command shims evolved over 10+ months of intensive daily use
Complete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, and rules evolved over 10+ months of intensive daily use
Complete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, and rules evolved over 10+ months of intensive daily use