- Home
- Skills
- Agents & Orchestration
- delegate-kit: 8 Claude Code subagents + playbook
More screenshots
Works with the AI Agents you already use
delegate-kit: 8 Claude Code subagents + playbook
Run Claude Code as an orchestrator: 8 subagents tiered by reasoning depth and cost, measured 6-10x cheaper per unit of work on large tasks.
$12.99
delegate-kit: 8 Claude Code subagents + playbook
Example session with this skill installed
I need to add rate limiting to all public API endpoints and update the documentation. Partition this work and start with the implementation plan.
- Read your context and instructions
- Compiled the delegate-kit
I have partitioned the objective into four work units across three execution layers. The schedule is stored in .delegate-kit/runs/api-rate-limit/schedule.json.
Partitioning Plan: API Rate Limiting
| Layer | ID | Title | Kind | Files | Est. Cost |
|---|---|---|---|---|---|
| 0 | W1 | Rate Limit Middleware | build | 3 | $0.12 |
| 1 | W2 | Apply to Public Routes | apply | 12 | $0.45 |
| 1 | W3 | Update API Docs | apply | 2 | $0.08 |
| 2 | W4 | Verify & Load Test | verify | 15 | $0.30 |
The partitioner has identified a shared middleware bottleneck in src/middleware/auth.ts. I will spawn the executer for
W1 first to establish the contract before parallelizing the application to routes.
Next steps
- Review the
schedule.jsonfor file hit accuracy. - Spawn the
executerfor[W1]using the generated middleware spec. - Run
dk benchafter the first layer to calibrate cost estimates.
Connects securely to your tools. The creator never sees your data.
About this skill
Stop burning expensive context on long Claude Code sessions. Large objectives often lead to massive context accumulation, driving up token costs and slowing down response times. This skill provides a specialized orchestration layer that delegates work to a fleet of eight tiered subagents, each optimized for specific reasoning depths and context costs.
What it does
- Multi-agent delegation routes work to eight specific subagent types including thinkers, researchers, and executers.
- Cost optimization: measured across 1,233 real Claude Code sessions, running as the director cut cost 6-10x per unit of work on objectives past ~35 tool calls, because the expensive model never accumulates a context. Below that line it costs more - full numbers, both directions, are in
reference/measurements.md. - Automated partitioning splits wide, multi-file changes into independent work units and parallel execution clusters.
- Web-enabled research provides a dedicated agent for fetching external documentation and API specs without repo access overhead.
- Defect hunting fans out cheap, disposable agents to sweep a listed set of files or a diff for real defects (never style).
How it works
- Setup installs the agent definitions and Python-based partitioning tools to the local
~/.claudedirectory. - Orchestration initiates a session using the
directoragent to manage the high-level objective and delegation logic. - Partitioning uses the
partitionerto map out complex tasks into aschedule.jsonbefore any implementation begins. - Execution spawns targeted workers (thinker, executer, simple-tasks) to perform isolated units of work and report findings by reference.
Frameworks & tools
The kit requires Claude Code and Python 3. It utilizes built-in shell tools like grep, bash, and sed, with optional enhanced support for Serena and graphify MCP servers.
Why this beats prompting it yourself
Writing manual prompts for subagents requires constant context management to prevent token bloat. This skill provides a formal protocol for "relay by reference," moving payloads through the filesystem instead of the chat history.
Use cases
- Refactoring large subsystems where a single agent would exceed context limits.
- Performing parallel bug sweeps across dozens of files simultaneously.
- Implementing features that require deep external API research before coding.
- Automating mechanical chores like git management and multi-hop builds.
Known limitations
Claude Code only: the director and the per-agent model pins rely on Claude Code subagents. Requires a manual installation step and a new session start to load agent definitions. Subagents are instructed not to run destructive git commands; this package installs no hooks, so that rule is enforced by their instructions only.
How to use
Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scanned
Verified clean 13 days ago
- Passed all security checks, Safe to install
Requires