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 bigu1/grok-plugin-codex --skill grok-workflowsgit clone --depth 1 https://github.com/bigu1/grok-plugin-codexWrote 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/bigu1/grok-plugin-codex/grok-workflows)<a href="https://agentmods.dev/skills/bigu1/grok-plugin-codex/grok-workflows"><img src="https://agentmods.dev/badge/skills/bigu1/grok-plugin-codex/grok-workflows/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/bigu1/grok-plugin-codex/grok-workflows"><img src="https://agentmods.dev/badge/skills/bigu1/grok-plugin-codex/grok-workflows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00020 | $0.00221 |
| Opus 5.5 | $0.00008 | $0.00088 |
| Sonnet 5.5 | $0.00004 | $0.00044 |
| Haiku 4.5 | $0.00002 | $0.00022 |
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 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.
This is a copy
100% identical to grok-workflows — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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
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 · 31 lines · 20 tokens per session scan A 47d308b0332a
grok-workflows is a skill published in the GitHub repository bigu1/grok-plugin-codex (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 20 tokens to every session and 221 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to grok-workflows, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
gpt-5-4-prompting
Internal guidance for composing Codex and GPT-5.4 prompts for coding, review, diagnosis, and research tasks inside the Grok Codex plugin.
codex-result-handling
Internal guidance for presenting Codex helper output back to the user.
grok-subagent
Delegate bounded coding, investigation, review, implementation, and real-time X/Reddit/web research tasks from Codex to the locally authenticated Grok Build CLI. Use when the user asks Codex to consult Grok, use Grok as a subagent, compare independent model conclusions, spend SuperGrok quota on useful project work…
delegate-to-grok
Delegate coding, repository inspection, comparisons, web research, and public X search from Codex to the locally installed Grok Build CLI on Windows. Use when a user asks to run or consult Grok, resume Grok Build authentication, compare Codex and Grok, inspect or modify a project with Grok, or perform public X…
grok-prompting
Internal guidance for composing Grok Build prompts for coding, review, diagnosis, and research tasks inside the Grok Claude Code plugin.
grok-bridge
Delegate any substantial local task to Grok Build as one durable logical job, in a repository or a non-repository workspace, and retrieve its genuine final result across turn, token, context, and caller-session boundaries. Use when the user asks for Grok/Grok Build, an independent builder/tester/reviewer/researcher…