delegation-orchestrator

delegation-orchestrator is a skill for Claude Code, Codex from dailyaiagents-cpu/dailyai-os. It costs 88 tokens per session (1,243 once invoked), scanned A, original, MIT.

A skill for routing blocked work from one software agent to another specialist. The blocked agent writes a JSON delegation request, and a background process dispatches it to the named agent.

In plain words
What is it for?
Creating pending delegation requests, sending tasks to named agents such as operations or research, handling session or access problems, and moving failed requests after the retry limit.
Why use it?
It prevents a specialist from repeatedly retrying a problem that another agent is better placed to solve, while limiting retries and tracking failures.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for openclaw. Also seen: built for openclaw.

Good fit Creating pending delegation requests, sending tasks to named agents such as operations or research, handling session or access problems, and moving failed requests after the retry limit.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dailyaiagents-cpu/dailyai-os/delegation-orchestrator
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 dailyaiagents-cpu/dailyai-os --skill delegation-orchestrator
Clone the repo
git clone --depth 1 https://github.com/dailyaiagents-cpu/dailyai-os

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 delegation-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/skills/dailyaiagents-cpu/dailyai-os/delegation-orchestrator/github.svg)](https://agentmods.dev/skills/dailyaiagents-cpu/dailyai-os/delegation-orchestrator)
Your own site
<a href="https://agentmods.dev/skills/dailyaiagents-cpu/dailyai-os/delegation-orchestrator"><img src="https://agentmods.dev/badge/skills/dailyaiagents-cpu/dailyai-os/delegation-orchestrator/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 delegation-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/skills/dailyaiagents-cpu/dailyai-os/delegation-orchestrator"><img src="https://agentmods.dev/badge/skills/dailyaiagents-cpu/dailyai-os/delegation-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 88 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,243 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.00088 $0.01243
Opus 5 $0.00044 $0.00622
Sonnet 5 $0.00018 $0.00249
Haiku 4.5 $0.00009 $0.00124

Measured 12d ago against content hash 042062c61d3c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

delegation-orchestrator 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 12d 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.

skills/delegation-orchestrator/SKILL.md · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

delegation-orchestrator

Why this exists

When the outreach-paced specialist hits "linkedin session expired," it shouldn't loop trying to fix it itself. It should write a delegation: "ops, please run session-keeper for linkedin." The ops agent runs the helper, opens the right gate, the user resolves it, outreach resumes. No specialist is stuck indefinitely; no Cooper-time wasted on routing.

This file is the convention + fault tree specialists read to know who to delegate to. The actual dispatch happens in tools/delegation_tick.py (daemon-tick, every 60s, permitted helper).

The convention

A specialist in a blocked state writes JSON to data/delegations/pending/<unix-timestamp>-<source>.json:

{
  "source_agent": "outreach-paced",
  "next_action": "ops",
  "task": "run session-keeper for linkedin target",
  "context_diff": "session-keeper reports linkedin status=expired since 2026-05-02T...",
  "priority": "high",
  "max_attempts": 2
}

Fields:

  • source_agent — who hit the block (informational)
  • next_action — the openclaw agent id who should help (e.g., ops, accountant, research)
  • task — single-message instruction; daemon-tick passes this verbatim to openclaw agent --agent <next_action> -m "<task>"
  • context_diff — optional, appended to task if present (keeps requests small)
  • prioritylow|medium|high (informational; daemon-tick doesn't reorder)
  • max_attempts — int, default 2

The daemon-tick (tools/delegation_tick.py):

  1. Polls data/delegations/pending/ every 60s
  2. For each request: attempts++ check vs max_attempts
  3. Calls openclaw agent --agent <next_action> -m "<task>" --timeout 120 --json
  4. On rc=0: moves to data/delegations/done/
  5. On rc≠0 with attempts < max: writes request back, retries next tick
  6. On attempts ≥ max: moves to data/delegations/failed/ with final_status: max-attempts-exhausted

Fault tree (specialists read this to know who to delegate to)

Source agent Trigger next_action task
outreach-paced linkedin session expired ops "run session-keeper for linkedin target"
hermes-inbox-router reddit poll returns 401 ops "rotate reddit credentials; verify session-keeper for reddit"
research paywall hit on <publisher> accountant "do we have a subscription to <publisher>?"
sales LinkedIn DM rate-limit ops "rotate session or switch surface for linkedin"
sales Reddit account suspension ops "check reddit account state"
content image-gen quota exceeded ops "check API key state for <provider>"
ops ollama model unreachable ops "run model-warmth-keeper recovery"
accountant Stripe webhook failed signature ops "check STRIPE_WEBHOOK_SECRET freshness"

Read the full file on GitHub · 111 lines

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. 12d ago First seen · 111 lines · 88 tokens per session scan A 042062c61d3c

Subscribe to this mod's changes

delegation-orchestrator is a skill published in the GitHub repository dailyaiagents-cpu/dailyai-os (0 stars, last pushed 4mo ago), licensed MIT. It adds 88 tokens to every session and 1,243 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens