A command for handing an investigation or requested coding task to a Grok Build helper agent. It passes the user’s request to that agent and returns its response.

Delegating research, diagnosis, implementation requests, or longer background tasks to Grok Build.

It lets another coding agent handle follow-up work while keeping the request and execution mode explicit.

delegate — Command for coding agents by xai-org: A command for handing an investigation or requested coding…

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.

agentmods

npx agentmods add commands/xai-org/grok-build-plugin-cc/delegate

Clone the repo

git clone --depth 1 https://github.com/xai-org/grok-build-plugin-cc

Or install grok-build, the plugin that ships this one along with the rest of its 2 skills, 8 commands, 1 agent, 2 hooks.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/xai-org/grok-build-plugin-cc/delegate.svg)](https://agentmods.dev/commands/xai-org/grok-build-plugin-cc/delegate)

Your own site

<a href="https://agentmods.dev/commands/xai-org/grok-build-plugin-cc/delegate"><img src="https://agentmods.dev/badge/commands/xai-org/grok-build-plugin-cc/delegate.svg" alt="Measured on agentmods" height="20"></a>

Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 931 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00020	$0.00931
Opus 5	$0.00010	$0.00465
Sonnet 5	$0.00004	$0.00186
Haiku 4.5	$0.00002	$0.00093

Measured 5d ago against content hash 899cf05e6302, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

delegate 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 5d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

delegate — 86% identical, 28 lines differ

plugins/grok-build/commands/delegate.md · 51 lines

What it actually says

Invoke the grok-build:grok-delegate subagent via the Agent tool (subagent_type: "grok-build:grok-delegate"), forwarding the raw user request as the prompt. grok-build:grok-delegate is a subagent, not a skill — do not call Skill(grok-build:grok-delegate) (no such skill) or Skill(grok-build:delegate) (that re-enters this command and hangs the session). The command runs inline so the Agent tool stays in scope; forked general-purpose subagents do not expose it. The final user-visible response must be Grok's output verbatim.

Raw user request: $ARGUMENTS

Execution mode:

If the request includes --background, run the grok-build:grok-delegate subagent in the background.
If the request includes --wait, run the grok-build:grok-delegate subagent in the foreground.
If neither flag is present, default to foreground.
Prefer bridge --background for long or open-ended work so the run records both bridgePid (Node worker) and agentPid (grok child).
--background and --wait are execution flags for Claude Code. Do not forward them to run, and do not treat them as part of the natural-language task text.
--model and --effort are runtime-selection flags. Preserve them for the forwarded run call, but do not treat them as part of the natural-language task text.
If the request includes --resume, do not ask whether to continue. The user already chose.
If the request includes --fresh, do not ask whether to continue. The user already chose.
Otherwise, before starting Grok, check for a resumable delegate thread from this Claude session by running:

node "${CLAUDE_PLUGIN_ROOT}/scripts/grok-bridge.mjs" run-resume-candidate --json

If that helper reports available: true, use AskUserQuestion exactly once to ask whether to continue the current Grok thread or start a new one.
The two choices must be:
- Continue current Grok thread
- Start a new Grok thread
If the user is clearly giving a follow-up instruction such as "continue", "keep going", "resume", "apply the top fix", or "dig deeper", put Continue current Grok thread (Recommended) first.
Otherwise put Start a new Grok thread (Recommended) first.
If the user chooses continue, add --resume before routing to the subagent.
If the user chooses a new thread, add --fresh before routing to the subagent.
If the helper reports available: false, do not ask. Route normally.

Operating rules:

The subagent is a thin forwarder only. It should use one Bash call to invoke node "${CLAUDE_PLUGIN_ROOT}/scripts/grok-bridge.mjs" run ... and return that command's stdout as-is.
Return the Grok bridge stdout verbatim to the user.
Do not paraphrase, summarize, rewrite, or add commentary before or after it.
Do not ask the subagent to inspect files, monitor progress, poll /grok-build:runs, fetch /grok-build:show, call /grok-build:stop, summarize output, or do follow-up work of its own.
Leave --effort unset unless the user explicitly asks for a specific reasoning effort.
Leave the model unset unless the user explicitly asks for one.
Leave --resume and --fresh in the forwarded request. The subagent handles that routing when it builds the run command.
If the helper reports that Grok is missing or unauthenticated, stop and tell the user to run /grok-build:check.
If the user did not supply a request, ask what Grok should investigate or fix.

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.

5d ago First seen · 51 lines · 20 tokens per session scan A 899cf05e6302

Subscribe to this mod's changes

delegate is a command published in the GitHub repository xai-org/grok-build-plugin-cc (236 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 20 tokens to every session and 931 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-30.

Building agents

delegate

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

git

checklist

clarify

specify

analyze

converge