delegate-skills is a toolkit for assigning coding tasks to separate agent command-line tools while keeping control of review and commits. It is for developers who want to organize installed implementers into lanes for work such as features, tests, or UI, then delegate tasks by lane or directly. The catalogue entries define the setup and delegation workflows.
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 amElnagdy/delegate-skills --skill delegate-setupgit clone --depth 1 https://github.com/amElnagdy/delegate-skillsWrote 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/amelnagdy/delegate-skills/delegate-setup)<a href="https://agentmods.dev/skills/amelnagdy/delegate-skills/delegate-setup"><img src="https://agentmods.dev/badge/skills/amelnagdy/delegate-skills/delegate-setup/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/amelnagdy/delegate-skills/delegate-setup"><img src="https://agentmods.dev/badge/skills/amelnagdy/delegate-skills/delegate-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00100 | $0.02588 |
| Opus 5.5 | $0.00040 | $0.01035 |
| Sonnet 5.5 | $0.00020 | $0.00518 |
| Haiku 4.5 | $0.00010 | $0.00259 |
Grade A, and why
delegate-setup 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delegate Setup
You are the orchestrator in setup mode. Discover installed implementer CLIs, propose a fleet of lanes, and write configuration only after the user approves.
This skill does not dispatch coding work. It only authors the lane map.
One concept: lanes. Never say “routes.”
Example lane: feature → implementer opencode, model opencode/grok, variant high
(OpenCode uses variant for reasoning intensity, not effort).
When NOT to use this
- The user wants a task implemented — use the matching
*-delegateskill instead. - A one-off model change on a single dispatch — pass
--model/--effort/--varianton that relay.
Hard rules
- Every lane must include
implementer. - Put dials on the same object (
model,effortorvariant, …) only if that implementer supports them — see references/schema.md. - Show a human-readable lane table and the full JSON before every write; re-show after every tweak.
- Write only after an explicit approval (“yes”, “approve”, “write it”).
- Ask scope unless already clear: global (all projects) vs this repo only. Never create a project file just because cwd is a git repo. If there is no git repo, default to global and say so.
- Do not invent model identifiers.
- In interview or usage-scan mode, never write any dial the user did not give you and the schema does not require — omit it, so the CLI’s or relay’s own default applies.
- Prefer 3–5 useful lanes over a kitchen-sink map.
- Never edit
AGENTS.md,CLAUDE.md, or other user agent-instruction files. - Never run a
*-delegaterelay from this skill.
(<skill-dir> is this skill’s install directory — the folder that contains this SKILL.md.)
Flow
discover → load → grounding menu → propose (with Basis) → scope → approve → write
1. Discover
node "<skill-dir>/scripts/discover.mjs"
Summarize installed vs missing, auth (true / false / null = unknown), and whether models were
reported, aliases (curated aliases in the registry, not live discovery — full model names also
work), unsupported, or failed.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 200 lines · 100 tokens per session scan A adf510d3c3d5
delegate-setup is a skill published in the GitHub repository amElnagdy/delegate-skills (2,441 stars, last pushed 6d ago), licensed MIT. It adds 100 tokens to every session and 2,588 once invoked, about $0.0004 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-30.
Other skills, from other repositories
openai-docs
Use when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, latest/current/default-model prompting guidance, or model upgrade and prompt-upgrade guidance; use…
visualize
Create visualizations and interactive tools directly in conversation. Use when asked to show how something works, make simulators or labs, maps, plots, charts or graphs, comparisons, UI mockups, scenarios, adjustable inputs, and exploration beyond regular text.
doc-typeset
A document formatter that turns text and design settings into complete, styled HTML. It includes templates for contracts, academic papers, official documents, business reports, meeting notes, research reports, and annual reports.
tdoc-orchestrator
A workflow coordinator for creating and formatting documents, then converting HTML documents into Word files. It identifies the user's document task and sends each stage to the appropriate specialist.
3D模型与视频特效
A tool for generating 3D models from text or images and applying preset animated effects to pictures. It does not generate ordinary images or full videos.
Spreadsheets
Create, edit, analyze, and verify standalone spreadsheet files or Google Sheets-ready workbooks, including .xlsx, .xls, .csv, and .tsv. Do not use for live controlling Microsoft Excel app or a live Excel session.