Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Delegate tasks to Codex and Gemini directly from within Claude Code.
| Date | Stars |
|---|---|
| 2026-07-31 | 984 |
| 2026-08-05 | 986 |
| 2026-08-06 | 986 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
0.0
growth rate 0.00%/day
# Claude Delegator
GPT expert subagents for Claude Code. Five specialists that can analyze AND implement—architecture, security, code review, and more.
[](LICENSE)
[](https://github.com/jarrodwatts/claude-delegator/stargazers)
## Install
Inside a Claude Code instance, run the following commands:
**Step 1: Add the marketplace**
```
/plugin marketplace add jarrodwatts/claude-delegator
```
**Step 2: Install the plugin**
```
/plugin install claude-delegator
```
**Step 3: Run setup**
```
/claude-delegator:setup
```
Done! Claude now routes complex tasks to GPT experts automatically.
> **Note**: Requires [Codex CLI](https://github.com/openai/codex) or [Gemini CLI](https://github.com/google/gemini-cli). Setup guides you through installation.
---
## What is Claude Delegator?
Claude gains a team of GPT and Gemini specialists via native MCP. Each expert has a distinct specialty and can advise OR implement.
**Note:** You can use either provider (GPT or Gemini), or both. The plugin will automatically detect which one is configured and route tasks accordingly.
| What You Get | Why It Matters |
|--------------|----------------|
| **5 domain experts** | Right specialist for each problem type |
| **GPT or Gemini** | Use your preferred model provider |
| **Dual mode** | Experts can analyze (read-only) or implement (write) |
| **Auto-routing** | Claude detects when to delegate based on your request |
| **Synthesized responses** | Claude interprets expert output, never raw passthrough |
### The Experts
| Expert | What They Do | Example Triggers |
|--------|--------------|------------------|
| **Architect** | System design, tradeoffs, complex debugging | "How should I structure this?" / "What are the tradeoffs?" |
| **Plan Reviewer** | Validate plans before you start | "Review this migration plan" / "Is this approach sound?" |
| **Scope Analyst** | Catch ambiguities early | "What am I missing?" / "Clarify the scope" |
| **Code Reviewer** | Find bugs, improve quality | "Review this PR" / "What's wrong with this?" |
| **Security Analyst** | Vulnerabilities, threat modeling | "Is this secure?" / "Harden this endpoint" |
### When Experts Help Most
- **Architecture decisions** — "Should I use Redis or in-memory caching?"
- **Stuck debugging** — After 2+ failed attempts, get a fresh perspective
- **Pre-implementation** — Validate your plan before writing code
- **Security concerns** — "Is this auth flow safe?"
- **Code quality** — Get a second opinion on your implementation
### When NOT to Use Experts
- Simple file operations (Claude handles these directly)
- First attempt at any fix (try yourself first)
- Trivial questions (no need to delegate)
---
## How It Works
```
You: "Is this authentication flow secure?"
↓
Claude: [Detects security question → selects Security Analyst]
↓
┌───────────────────────────────┐
│ mcp__codex__codex │
│ (or mcp__gemini__gemini) │
│ → Security Analyst prompt │
│ → Expert analyzes your code │
└───────────────────────────────┘
↓
Claude: "Based on the analysis, I found 3 issues..."
[Synthesizes response, applies judgment]
```
**Key details:**
- Each expert has a specialized system prompt (in `prompts/`)
- Claude reads your request → picks the right expert → delegates via MCP (GPT or Gemini)
- Responses are synthesized, not passed through raw
- Experts can retry up to 3 times before escalating
- Multi-turn conversations preserve context via `threadId` for chained tasks
### Multi-Turn Conversations
For chained implementation steps, the expert preserves context across turns:
```
Turn 1: mcp__*__* → returns threadId
Turn 2: mcp__*__*-reply(threadId) → expert Excerpt of 7,460 characters
Read on GitHub
Jarrod Watts · Australia
45
2
1
Would you bet a product on this? Bounded 0–100 and slow moving.
matched fp:e0e7e4678c025580, topic:gpt
matched fp:e0e7e4678c025580, topic:ai-agents
matched fp:e0e7e4678c025580, topic:mcp