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/cyzice/devs-codex/subagent-delegationnpx skills add CYZice/devs-codex --skill subagent-delegationgit clone --depth 1 https://github.com/CYZice/devs-codexWhat 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.00969 |
| Opus 5 | $0.00009 | $0.00485 |
| Sonnet 5 | $0.00004 | $0.00194 |
| Haiku 4.5 | $0.00002 | $0.00097 |
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 2d 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 — 149 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> "<prompt>"
devspace agents continue <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.
Use the returned logical agt_... ID with continue; provider session IDs and
prefixes are not interchangeable with logical agent IDs.
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.
continue <id> "<prompt>" sends a follow-up to an existing agent. Do not use
run <id> for continuation.
Continuation supports the same per-turn model and thinking overrides:
devspace agents continue <id> --model <model> "<prompt>"
devspace agents continue <id> --thinking <level> "<prompt>"
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.
The commands automatically start the internal devspace-agentd process when
needed. devspace serve is not required for local-agent execution. The daemon
owns shared agent sessions and provider runtimes for the configured DevSpace
state directory.
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.
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.
- 2d ago First seen · 149 lines · 18 tokens per session scan A 11d45746aa4e
subagent-delegation is a skill published in the GitHub repository CYZice/devs-codex (0 stars, last pushed 12d ago), licensed MIT. It adds 18 tokens to every session and 969 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…