Agent skill

Copilot Delegate

by amElnagdy in amElnagdy/delegate-skills

Delegate a coding task to the GitHub Copilot CLI (copilot) as a background implementer, then review its diff and land it yourself.

MITAuto-check passedDevelopment

Install Copilot Delegate

skills CLI
$ npx skills add amElnagdy/delegate-skills --skill copilot-delegate -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install amElnagdy/delegate-skills copilot-delegate --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/amElnagdy/delegate-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/copilot-delegate .claude/skills/copilot-delegate && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
copilot-delegate
GitHub stars
2.3k
Used in
1 other repo
Token cost
~1.8k tokens
SKILL.md length
796 words
Files
6 (incl. scripts, references)
Skills in repo
18
Repo updated
First seen
Licence
MIT

At a glance

Delegate a coding task to the GitHub Copilot CLI (copilot) as a background implementer, then review its diff and land it yourself.

  • Works in 5 steps: Write a brief → Dispatch → Wait for completion → …
  • Wants to delegate implementation work to Copilot - phrasings like have Copilot implement X
  • SKILL.md covers When NOT to use this, Prerequisites (check once), Choose the model (optional) and Choose the effort (optional), plus 4 more sections
  • Runs JavaScript scripts from its folder; calls git, node and npm; needs COPILOT_GITHUB_TOKEN and GH_TOKEN

What it does

Copilot Delegate is an agent skill from amElnagdy/delegate-skills. Delegate a coding task to the GitHub Copilot CLI (copilot) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Copilot - phrasings like "have Copilot implement X", "delegate this to copilot", "run it through Copilot CLI", or "use copilot to implement/fix/refactor" - or wants to run a queue of coding tasks through Copilot while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code…

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `references/dispatch-and-poll.md`, `references/multi-task-queues.md` and `references/review-and-land.md`). Compatibility notes: Requires the copilot CLI installed and authenticated (copilot login), Node 18+ to run the relay (the copilot CLI itself requires Node 22+), and git. The…

It sits in Development. The repository describes itself as: Delegate a coding task to a separate coding agent CLI, review the diff, land the commit yourself — one per implementer. The licence is MIT.

When your agent uses it

  • Wants to delegate implementation work to Copilot - phrasings like have Copilot implement X
  • Delegate this to copilot
  • Run it through Copilot CLI
  • Use copilot to implement/fix/refactor -

Example prompts

  • “have Copilot implement X”
  • “delegate this to copilot”
  • “run it through Copilot CLI”
  • “/copilot-delegate”

Requirements

  • Node.js
  • A credential in COPILOT_GITHUB_TOKEN
  • A credential in GITHUB_TOKEN
  • Compatibility (from SKILL.md): Requires the `copilot` CLI installed and authenticated (`copilot login`), Node 18+ to run the relay (the copilot CLI itself requires Node 22+), and git. The orchestrator must be able to run shell commands and read files.

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Write a brief
  2. Dispatch
  3. Wait for completion
  4. Review — do not trust the self-report
  5. Land it

What it can do on your machine

Read from SKILL.md and the folder at commit 8ef0210. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (JavaScript), which the agent can run.

    Shell commands in SKILL.md call:

    • git
    • node
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • COPILOT_GITHUB_TOKEN
    • GH_TOKEN
    • GITHUB_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires the `copilot` CLI installed and authenticated (`copilot login`), Node 18+ to run the relay (the copilot CLI itself requires Node 22+), and git. The orchestrator must be able to run shell commands and read files.

    From compatibility in the SKILL.md frontmatter.

Context cost

Copilot Delegate loads about 1.8k tokens when it runs, and up to ~6.9k if it reads all its reference files. Until then it costs about 144 tokens; SKILL.md has 796 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~144
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from amElnagdy/delegate-skills at commit 8ef0210, republished under its MIT licence (© amElnagdy). 796 words, ~1,791 tokens.

Download SKILL.mdSave it as .claude/skills/copilot-delegate/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
copilot-delegate
description
Delegate a coding task to the GitHub Copilot CLI (`copilot`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Copilot - phrasings like "have Copilot implement X", "delegate this to copilot", "run it through Copilot CLI", or "use copilot to implement/fix/refactor" - or wants to run a queue of coding tasks through Copilot while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.
compatibility
Requires the `copilot` CLI installed and authenticated (`copilot login`), Node 18+ to run the relay (the copilot CLI itself requires Node 22+), and git. The orchestrator must be able to run shell commands and read files.
license
MIT
metadata.version
0.5.0

Copilot Delegate

You are the orchestrator. Delegate a bounded coding task to a separate implementer — the GitHub Copilot CLI — then review what it produced and land it yourself. You write the brief and own the judgment; the implementer makes changes in its own session in a clean working tree; you verify and commit.

The loop needs only a shell command and file access, so any comparable orchestrator can drive it.

When NOT to use this

  • The task is small enough to do inline; delegation overhead is not worth it.
  • The copilot CLI is not installed or authenticated.
  • You need a hard sandbox. Copilot exposes sandbox controls, but they are upstream-experimental (MXC-based, controlled via the /sandbox command and settings, disabled by default) — this relay does not configure them. --read-only only disables edit tools (--mode plan); shell commands still run. If project files must not change at all, dispatch against a clean or isolated worktree.

Prerequisites (check once)

  1. Install copilot (npm install -g @github/copilot; the CLI requires Node 22+, the relay itself runs on Node 18+ — the relay probes copilot version).
  2. Authenticate: run copilot login (interactive web/device flow), or set COPILOT_GITHUB_TOKEN / GH_TOKEN / GITHUB_TOKEN in the environment.
  3. Confirm copilot version succeeds.
  4. Work in, or point --cd at, the target git repository.

Choose the model (optional)

Copilot picks a default model (auto). To choose another, pass --model <name>. The relay accepts letters, digits, and . _ : / - only (the value reaches a shell on Windows).

Choose the effort (optional)

Copilot supports a reasoning effort dial: --effort <level> with values low, medium, high, xhigh, or max. The relay rejects any other value before dispatch.

The loop

Run these five steps per task. Steps 1, 4, and 5 require judgment; 2 and 3 are mechanical.

1. Write a brief

Copilot sees only the text you send. It cannot read your conversation: the brief must stand alone with the goal, current state, what to change, what to leave untouched, the project's real gates, and a report contract. Keep each brief to a single task. Write it to a file and pass it as the relay's --brief. See references/writing-the-brief.md.

2. Dispatch

Use the bundled relay. It runs copilot -p with --output-format json --no-color --stream off, captures the JSONL event stream, and writes result.json.

bash
node "<skill-dir>/scripts/relay.mjs" --brief brief.txt --cd /path/to/repo
# choose a model:                    add --model <name>
# set reasoning effort:              add --effort <level>
# read-only planning pass:           add --read-only  (forces --mode plan)
# full tool autonomy:                add --allow-all-tools
# hard time limit (watchdog):        add --timeout 2h   (the 30m default suits brief runs)
# resume a session:                  add --session <id>  or  --resume-last
# see all options:                   node .../relay.mjs --help

The child's cwd pins the workspace. The relay writes artifacts under the system temp dir by default and never commits. See references/dispatch-and-poll.md.

3. Wait for completion

The relay blocks until copilot finishes. Run it with the orchestrator's background-command facility, or background it in the shell and poll for result.json. A pre-run usage error exits 2 and writes no result; a missing copilot exits 127 and writes status: "copilot_unavailable".

Completion means the process exited and result.json exists — trust process state and the working tree, not the progress display. Copilot's final assistant message is the finalMessage field of result.json.

Show full SKILL.md (323 more words)Show less
4. Review — do not trust the self-report
  • Re-run the project's gates yourself.
  • Read the diff against the brief, starting with touchedFiles.
  • Run relevant guard skills if installed.

See references/review-and-land.md.

5. Land it

If the work is good, commit it. The relay never commits — the diff and result.json are the record; run git status and git diff first to confirm exactly what changed. If the group has a PR flow, make the commit and push a branch; let human review happen. If the diff is wrong or incomplete, re-dispatch a corrected brief in a fresh run and review again.

Autonomy and permissions

Without --allow-all-tools, copilot auto-denies tool calls in headless mode: the process exits 0 but the relay detects the denial events and reports status: "failed" with the CLI's own error message and a hint to pass --allow-all-tools. This is the honest default — the orchestrator sees the failure rather than a silent no-op.

--allow-all-tools explicitly grants full tool autonomy. --read-only selects --mode plan, which disables edit tools so project files can't be changed by direct edits; it works without --allow-all-tools. Shell commands still run in plan mode, so it guards against edits, not against everything. The two flags are mutually exclusive.

Copilot also exposes sandbox controls, but they are upstream-experimental (MXC-based, controlled via the /sandbox command and settings, disabled by default). This relay does not configure them.

Authorization model

Delegation is something the human opts into. Once briefed, copilot works as a tool you approved use of. The boundary is: do not accept conclusions from the self-report; verify everything on disk. For anything touching credentials, production data, or irreversible operations, stop and ask the human first instead of encoding it in a brief.

References

© amElnagdy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (scripts, references) in skills/copilot-delegate of amElnagdy/delegate-skills.

  • SKILL.md
  • references/dispatch-and-poll.md
  • references/multi-task-queues.md
  • references/review-and-land.md
  • references/writing-the-brief.md
  • scripts/relay.mjs

Open the folder on GitHubat commit 8ef0210

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in amElnagdy/delegate-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Copilot Delegate next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Copilot Delegate compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Copilot Delegate this skillamElnagdy/delegate-skills2.3k1 repos~1.8kAutomated safety check: PassMIT
Vercel Composition Patternssupabase/supabase111k59 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 59 repos~726 tokens
    DevelopmentAuto-check passed
  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from amElnagdy/delegate-skills

All 18 skills in this repo
  • Aider Delegate

    amElnagdy/delegate-skills

    Delegate a coding task to Aider (aider) as a background implementer, then review its diff and land it yourself.

    2.3k GitHub starsUsed in 3 repos~3k tokens
    Auto-check passed
  • Codex Delegate

    amElnagdy/delegate-skills

    Delegate a coding task to the OpenAI Codex CLI as a background implementer, then review its diff and land it yourself.

    2.3k GitHub starsUsed in 3 repos~2.5k tokens
    Auto-check passed
  • Qoder Delegate

    amElnagdy/delegate-skills

    Delegate a coding task to the Qoder CLI (qodercli) as a background implementer, then review its diff and land it yourself.

    2.3k GitHub starsUsed in 3 repos~1.6k tokens
    Auto-check passed
  • Warp Delegate

    amElnagdy/delegate-skills

    Delegate a coding task to the Warp Agent CLI (oz) as a background implementer, then review its diff and land it yourself.

    2.3k GitHub starsUsed in 3 repos~2.6k tokens
    Auto-check passed
  • Agy Delegate

    amElnagdy/delegate-skills

    Delegate a coding task to the Google Antigravity CLI (agy) as a background implementer, then review its diff and land it yourself.

    2.3k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Claude Delegate

    amElnagdy/delegate-skills

    Delegate a coding task to a separate Claude Code CLI process or another Claude session as an implementer, then review its diff and land it yourself.

    2.3k GitHub starsUsed in 1 repo~2.4k tokens
    Auto-check passed

Categories

Questions about Copilot Delegate

What does Copilot Delegate do?

Delegate a coding task to the GitHub Copilot CLI (copilot) as a background implementer, then review its diff and land it yourself. Copilot Delegate is an agent skill from amElnagdy/delegate-skills. Delegate a coding task to the GitHub Copilot CLI (copilot) as a background implementer, then review its diff and land it yourself.

When should I use Copilot Delegate?

Copilot Delegate fits situations like: wants to delegate implementation work to Copilot - phrasings like have Copilot implement X; delegate this to copilot; run it through Copilot CLI; use copilot to implement/fix/refactor -.

How do I install Copilot Delegate in Claude Code?

Run `npx skills add amElnagdy/delegate-skills --skill copilot-delegate -a claude-code`. Or copy the skill folder (skills/copilot-delegate in amElnagdy/delegate-skills) into .claude/skills/copilot-delegate in your project. Claude Code loads it when a task matches its description.

How do I install Copilot Delegate in Codex?

Run `npx skills add amElnagdy/delegate-skills --skill copilot-delegate -a codex`. Or copy the skill folder (skills/copilot-delegate in amElnagdy/delegate-skills) into .agents/skills/copilot-delegate in your project. Codex loads it when a task matches its description.

Can I use Copilot Delegate in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add amElnagdy/delegate-skills --skill copilot-delegate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/copilot-delegate, .gemini/skills/copilot-delegate, .github/skills/copilot-delegate and .opencode/skills/copilot-delegate in your project.

What does Copilot Delegate need to run?

Going by SKILL.md and its folder, Copilot Delegate needs JavaScript for the scripts in its folder, the command-line tools its instructions call (git, node and npm) and credentials named COPILOT_GITHUB_TOKEN, GH_TOKEN and GITHUB_TOKEN. Our summary lists: Node.js; A credential in COPILOT_GITHUB_TOKEN; A credential in GITHUB_TOKEN. Compatibility (from SKILL.md): Requires the `copilot` CLI installed and authenticated (`copilot login`), Node 18+ to run the relay (the copilot CLI itself requires Node 22+), and git. The orchestrator must be able to run shell commands and read files..

Does Copilot Delegate access the network?

SKILL.md contains no URLs. Its commands use git and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Copilot Delegate safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Copilot Delegate use?

Copilot Delegate is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Copilot Delegate use?

About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.1k tokens, read only when the agent opens those files.

What are the alternatives to Copilot Delegate?

Skills that share tags, products or a category with Copilot Delegate: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Copilot Delegate?

amElnagdy (a GitHub user) maintains it in amElnagdy/delegate-skills, which has 2,328 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 7, 2026.

Source: amElnagdy/delegate-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.