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/cooky-dance/devspace-local-artifacts/subagent-delegationnpx skills add cooky-dance/devspace-local-artifacts --skill subagent-delegationgit clone --depth 1 https://github.com/cooky-dance/devspace-local-artifactsWrote 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/cooky-dance/devspace-local-artifacts/subagent-delegation)<a href="https://agentmods.dev/skills/cooky-dance/devspace-local-artifacts/subagent-delegation"><img src="https://agentmods.dev/badge/skills/cooky-dance/devspace-local-artifacts/subagent-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 | $0.00018 | $0.00824 |
| Opus 5 | $0.00009 | $0.00412 |
| Sonnet 5 | $0.00004 | $0.00165 |
| Haiku 4.5 | $0.00002 | $0.00082 |
Grade A, and why
subagent-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 5d 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.
This is a copy
100% identical to subagent-delegation — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Subagent Delegation
Use this skill when the user explicitly asks to delegate work to another coding agent, use a named subagent, get a second opinion, compare approaches, or run a subagent-like workflow.
Do not use subagents silently. Tell the user when another subagent is being used.
Core commands
Use only these commands for normal delegation:
devspace agents ls
devspace agents run <profile-or-provider-or-id> "<prompt>"
devspace agents show <id>
ls shows existing subagent sessions for the current workspace. DevSpace scopes
it automatically from the shell environment injected by the workspace tool.
run <profile> "<prompt>" starts a new configured profile and prints a
DevSpace agent id.
run <provider> "<prompt>" starts a raw built-in provider when no configured
profile is needed. Built-in providers are listed by open_workspace.
run <id> "<prompt>" sends a follow-up to an existing agent.
show <id> prints status and the latest response. If the agent is still
running, show waits briefly. If there is still no final response, call show
again later.
Do not run provider CLIs such as codex, claude, opencode, pi,
cursor-agent, or copilot directly unless you are explicitly debugging
DevSpace agent integration.
Choosing a profile
Choose profiles from the compact subagent profile catalog returned by
open_workspace. Use the profile name with devspace agents run. If no
profile fits and delegation is still appropriate, use a built-in provider name
from open_workspace.
Profiles may declare a model and optional thinking level. To override the
configured/default provider model or thinking level for a run, pass --model
or --thinking:
devspace agents run <profile-or-provider> --model <model> "<prompt>"
devspace agents run <profile-or-provider> --thinking <level> "<prompt>"
Use --thinking only when the user asks for a specific reasoning depth or when
the task clearly needs a different effort than the configured profile default.
Thinking values are provider-specific passthrough values. Use names supported by
the selected local agent harness; DevSpace does not translate values between
providers.
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.
- 5d ago First seen · 133 lines · 18 tokens per session scan A e26ad30ef0cd
subagent-delegation is a skill published in the GitHub repository cooky-dance/devspace-local-artifacts (3 stars, last pushed 27d ago), licensed MIT. It adds 18 tokens to every session and 824 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to subagent-delegation, differing in 0 lines, and is treated as a copy.
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…