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.
npx agentmods add skills/axgord/claude-workflow/task-delegationnpx skills add AxGord/claude-workflow --skill task-delegationgit clone --depth 1 https://github.com/AxGord/claude-workflowWrote 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.
[](https://agentmods.dev/skills/axgord/claude-workflow/task-delegation)<a href="https://agentmods.dev/skills/axgord/claude-workflow/task-delegation"><img src="https://agentmods.dev/badge/skills/axgord/claude-workflow/task-delegation.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00013 | $0.03069 |
| Opus 5 | $0.00006 | $0.01535 |
| Sonnet 5 | $0.00003 | $0.00614 |
| Haiku 4.5 | $0.00001 | $0.00307 |
Grade A, and why
task-delegation 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Delegation
Quick Check
- Independent parts? → if < 2, do it yourself
- Interfaces known? → if no, do it yourself
- Different skills needed? → if same, maybe don't split
- Plan ready? → if no, plan first
3+ yes → delegate
Model Selection (mandatory)
ALWAYS pass an explicit model to the Agent tool — never let a spawn
silently inherit the session model (the session tier is the orchestrator's;
paying it per worker doubles cost for no gain). Never haiku. Pick by
cost-of-error × mechanical safety net: where a linter/test-suite/compiler
catches mistakes, sonnet suffices; where nothing mechanical guards the
output, opus.
| Spawn | Model |
|---|---|
| Review batches with a lint report (.hx+hxq), instruction/config files, routine code | sonnet |
| Review of macro-heavy / concurrency / engine-critical / no-linter code | opus |
| Finding verification (one skeptic over aggregated findings) | opus |
| Code-writing agents: non-trivial logic | opus |
| Code-writing agents: mechanical edits from a detailed plan | sonnet |
| Explore / locate fan-out (returns locations, not judgements) | sonnet |
| Build/test/repro runners (verbatim-quote reporting) | sonnet |
| Web-research fetch/extract fan-out (synthesis stays in the parent) | sonnet |
| Analytical judgement subagents (blast-radius verdicts, design recon) | opus |
On overlap, opus wins: a lint-covered batch that is ALSO macro-heavy / concurrency / engine-critical goes to opus — a style/structure linter does not mechanically guard against races or codegen-correctness bugs.
Top-Tier Orchestrator Unloading
When THIS session runs on the top model tier — the STRONGEST model the harness offers (you know your own model from your system prompt; an opus/sonnet session is NOT top-tier and skips this section) — your output is JUDGMENT, not code: the session context is re-read every turn at top-tier rates, so file bodies must not flow through it:
- The PLAN is built HERE, inline — it is the condensate of the user dialog (intent, rejected options, constraints) that no brief can carry; and the planner must be the dispatcher (contracts drift when split). Recon FOR the plan delegates (Explore/Plan agents); the plan does not. A top-tier plan sub-agent is an escalation tool for WEAKER main sessions, never for a top-tier one (it would pay for the same understanding twice).
- CODE above ~30 changed lines → implementer agent(s): a COUPLED change goes to ONE implementer carrying the whole plan + contracts (never fan out a coupled set per-file); independent files fan out in parallel as usual.
- Implementer tier = f(plan detail × mechanical net): a detailed plan
(exact edits, contracts, order) + a net (linter/tests/compiler) →
sonnet— implementation became mechanics; the plan deliberately leaves in-implementation freedom (algorithms, macros, concurrency, engine-critical) or there is no net →opus. The economics of the scheme: top-tier judgment buys a plan so precise that a cheap model can write from it. - Stays inline: tiny edits (≤~30 lines — a yaml line, a config tweak, memory notes) where agent round-trip costs more than it saves; and PLAN-CLASS text generally (prompts, skill instructions, briefs, plans, memory) — that text IS the orchestrator's own product.
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.
- 6d ago First seen · 222 lines · 13 tokens per session scan A 76e5d63ac7de
task-delegation is a skill published in the GitHub repository AxGord/claude-workflow (5 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 3,069 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…