delegating-to-subagents

delegating-to-subagents is a skill for Claude Code, Codex from New1Direction/korgex. It costs 19 tokens per session (258 once invoked), scanned A, original, MIT.

A set of guidelines for splitting independent pieces of work between separate coding subagents and combining their results.

In plain words
What is it for?
Use it when investigating separate bugs, reviewing unrelated files, or implementing independent parts of a larger task.
Why use it?
It keeps each piece focused and can reduce confusion when different files or subsystems can be handled independently.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

Good fit Use it when investigating separate bugs, reviewing unrelated files, or implementing independent parts of a larger task.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/new1direction/korgex/delegating-to-subagents
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add New1Direction/korgex --skill delegating-to-subagents
Clone the repo
git clone --depth 1 https://github.com/New1Direction/korgex

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for delegating-to-subagents

README.md
[![agentmods](https://agentmods.dev/badge/skills/new1direction/korgex/delegating-to-subagents/github.svg)](https://agentmods.dev/skills/new1direction/korgex/delegating-to-subagents)
Your own site
<a href="https://agentmods.dev/skills/new1direction/korgex/delegating-to-subagents"><img src="https://agentmods.dev/badge/skills/new1direction/korgex/delegating-to-subagents/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for delegating-to-subagents

Your own site · 80×15
<a href="https://agentmods.dev/skills/new1direction/korgex/delegating-to-subagents"><img src="https://agentmods.dev/badge/skills/new1direction/korgex/delegating-to-subagents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 258 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.00258
Opus 5 $0.00010 $0.00129
Sonnet 5 $0.00004 $0.00052
Haiku 4.5 $0.00002 $0.00026

Measured 9d ago against content hash 6f49d94771dc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

delegating-to-subagents scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

src/skills_builtin/delegating-to-subagents/SKILL.md · 23 lines

What it actually says

When a task has independent parts, delegate them to subagents (the Agent tool) instead of doing everything in one context. Each gets an isolated context window, so you stay focused on coordination.

  1. Decide if it fits. Use subagents when parts are INDEPENDENT (different files/subsystems/bugs) and can run without each other's intermediate state. If they share tightly-coupled state, do it inline instead.
  2. Scope each one tightly. Give each subagent: a single clear goal, the exact context it needs (don't assume it sees this conversation), constraints ("don't touch X"), and what to return. Narrow scope = reliable result.
  3. Dispatch in parallel for independent work; sequential only when one depends on another's output.
  4. Aggregate. Read each result, reconcile conflicts, and verify the combined result yourself — subagents can make systematic mistakes. Then run the suite.
  5. Keep the user's view current: reflect delegated work in your task checklist.
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 23 lines · 19 tokens per session scan A 6f49d94771dc

Subscribe to this mod's changes

delegating-to-subagents is a skill published in the GitHub repository New1Direction/korgex (5 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 258 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.