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 skills add CYZice/devs-codex --skill subagent-delegationgit clone --depth 1 https://github.com/CYZice/devs-codexWrote 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/cyzice/devs-codex/subagent-delegation)<a href="https://agentmods.dev/skills/cyzice/devs-codex/subagent-delegation"><img src="https://agentmods.dev/badge/skills/cyzice/devs-codex/subagent-delegation/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.
<a href="https://agentmods.dev/skills/cyzice/devs-codex/subagent-delegation"><img src="https://agentmods.dev/badge/skills/cyzice/devs-codex/subagent-delegation.svg" alt="Reviewed on agentmods" width="80" 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.00018 | $0.00969 |
| Opus 5.5 | $0.00007 | $0.00388 |
| Sonnet 5.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 1mo 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.
- 1mo 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 1mo ago), licensed MIT. It adds 18 tokens to every session and 969 once invoked, about $0.0001 per session on Opus 5.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
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.