grok-workflows

A guide for running repeatable Grok multi-agent workflows, which are scripted jobs that coordinate several coding agents.

In plain words
What is it for?
Use it to list workflows, validate one, or run it with named arguments and optional background execution.
Why use it?
It helps run structured parallel reviews or batches consistently instead of manually recreating the same sequence of agent tasks.

Skill for Claude CodeCodex

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 skills/stdevmac/grok-in-codex/grok-workflows
Any agent
npx skills add stdevMac/grok-in-codex --skill grok-workflows
Clone the repo
git clone --depth 1 https://github.com/stdevMac/grok-in-codex

Made for: Claude Code, Codex.

Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 221 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.

ModelPer sessionOnce invoked
Fable 5 $0.00020 $0.00221
Opus 5 $0.00010 $0.00111
Sonnet 5 $0.00004 $0.00044
Haiku 4.5 $0.00002 $0.00022

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

Security

Grade A, and why

grok-workflows 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 2d 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:

plugins/grok/skills/grok-workflows/SKILL.md · 31 lines

What it actually says

Grok workflows

Workflows are deterministic Rhai scripts under .grok/workflows/ or ~/.grok/workflows/ that orchestrate parallel subagents via Grok’s workflow tool.

When to use

  • Multi-dimension review (correctness + error handling + performance) with adversarial verify
  • Bounded fan-out over a known work list
  • Repeatable pipelines the user wants by name

How

grok_workflow list
grok_workflow run <name> --arg key=value --background
grok_workflow run <name> --validate-only

Do not reimplement workflow logic in Claude. The companion hands a prompt that tells Grok to use the workflow tool.

Prefer over multi-rescue when

  • The work is a named recipe with structured phases
  • You need agent budget caps and deterministic fan-out
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. 2d ago First seen · 31 lines · 20 tokens per session scan A 47d308b0332a

Subscribe to this mod's changes

grok-workflows is a skill published in the GitHub repository stdevMac/grok-in-codex (22 stars, last pushed 29d ago), licensed Apache-2.0. It adds 20 tokens to every session and 221 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.

Related

Other skills, from other repositories

grok-routing

When to reach for Grok Build rather than doing the work in Claude Code — the routing tiers (manual, second-opinion, reach, offload-first, delegate-write), what each one covers, what it costs, and how to call it. Load this before offloading work, before asking for a second opinion, and before delegating anything to…

kai-wedekind/claude-code-grok-bridge · 92 tokens

grok-cli-runtime

How to delegate tasks to the Grok CLI from Claude Code via the grok-companion runtime. Use when forwarding a coding, debugging, or review task to Grok, when driving grok headlessly, or when the grok-rescue subagent or /grok-cc:rescue command needs to invoke the companion. Covers task vs read-only runs, foreground vs…

zachdunn/grok-plugin-claude-code · 89 tokens

codex-delegate

Delegate coding, review, diagnosis, or follow-up work to the local Codex CLI from Grok Build. Use when the user asks to command Codex, hand work to Codex, run /codex, /codex:rescue, /codex:review, or says 让 Codex 干、叫 Codex 审查、 指挥 Codex.

jinxlzc/grok-codex-plugin · 82 tokens

grok-delegate-runtime

Internal helper contract for calling the grok-bridge runtime from Claude Code.

kai-wedekind/claude-code-grok-bridge · 20 tokens

grok-prompting

How to shape a good prompt before delegating to Grok via the grok-rescue subagent or /grok-cc:rescue. Use when tightening a vague user request into a crisp Grok task. Covers stating the goal, constraints, acceptance criteria, and scope so a one-shot headless Grok run succeeds.

zachdunn/grok-plugin-claude-code · 73 tokens

grok-result-handling

Internal guidance for presenting Grok companion output (delegate results and reviews) back to the user.

zachdunn/grok-plugin-claude-code · 24 tokens