Makfly Cc Delegator
cc-delegator is a Claude Code plugin for the Ship phase that orchestrates five multi-provider LLM expert subagents for architecture, security, code review, scope, and planning.
by MakFly · github.com/MakFly/cc-delegator
Install cc-delegator when you want Claude Code to call five external LLM expert subagents—Architect, Security, Code Review, Scope, and Plan—through any OpenAI- or Anthropic-compatible API.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install makfly-cc-delegator@MakFly/cc-delegatorBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:MakFly/cc-delegator") and the paste-ready config with skillselion.get_install_config("plugin:MakFly/cc-delegator").
What it does
MakFly cc-delegator is a Claude Code plugin that turns your main session into an orchestrator for five LLM-backed expert subagents, each tuned to a different pre-release concern. Instead of prompting one model to wear every hat, you delegate architecture questions, security scrutiny, code review, scope tightening, and planning to separate calls over APIs you already use—OpenAI, Anthropic, Codex-compatible endpoints, and related stacks called out in the catalog. Solo builders benefit when they lack a human review bench but still want disciplined gates before shipping SaaS or agent features. The plugin count is one because the value is the delegation fabric, not a pile of unrelated slash skills. Setup is intermediate: you must wire API keys and provider routes, then invoke the delegator when a feature branch needs a second opinion without leaving Claude Code. Skillselion shelves it under Ship/review while acknowledging architect and plan flows during build planning.
Highlights
- Single plugin exposing five named expert subagents: Architect, Security, Code Review, Scope, and Plan.
- Multi-provider delegation to OpenAI, Anthropic, Codex, and compatible APIs via MCP-style orchestration keywords.
- Keeps Claude Code as coordinator while specialists run on external models you configure.
- Targets pre-ship quality: architecture sanity, security pass, review, scope control, and planning.
- Community catalog entry with pluginCount: 1 focused delegator rather than a broad skill pantry.
Why builders use it
One Claude session cannot reliably play senior architect, security auditor, and reviewer at once before you ship.
After configuration, you delegate focused expert runs to external models and fold their answers back into your Claude Code workflow before merge or launch.
At a glance
- Type - Plugin in AI Agents.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is cc-delegator for?
It is for Claude Code users who want MakFly’s five specialist subagents—Architect, Security, Code Review, Scope, and Plan—backed by their own OpenAI or Anthropic-compatible APIs.
When should I use cc-delegator?
Use it before shipping or merging when you need delegated architecture, security, review, scope, or planning opinions separate from your primary Claude thread.
How do I add cc-delegator to my agent?
Install the MakFly/cc-delegator plugin in Claude Code, configure your provider API keys and compatible endpoints, then invoke the delegator commands to spawn the expert subagents.
Comments
Share how you use makfly-cc-delegator, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.