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 agentmods add skills/iml1s/agent-cli-skills/grok-cli-agentnpx skills add ImL1s/agent-cli-skills --skill grok-cli-agentgit clone --depth 1 https://github.com/ImL1s/agent-cli-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/iml1s/agent-cli-skills/grok-cli-agent)<a href="https://agentmods.dev/skills/iml1s/agent-cli-skills/grok-cli-agent"><img src="https://agentmods.dev/badge/skills/iml1s/agent-cli-skills/grok-cli-agent.svg" alt="Measured on agentmods" 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 | $0.00088 | $0.00607 |
| Opus 5 | $0.00044 | $0.00303 |
| Sonnet 5 | $0.00018 | $0.00121 |
| Haiku 4.5 | $0.00009 | $0.00061 |
Grade A, and why
grok-cli-agent 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 3d 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.
What it actually says
Grok Build CLI (grok) Executor
When to use
- User wants grok / Grok Build as the coding agent
- Need Grok
spawn_subagent,--agentsJSON, or--worktreeisolation from an orchestrator
Wrapper
./grok-exec.sh -C /path/to/repo -t 1800s "Implement X. NO git."
./grok-exec.sh -r -C /path/to/repo "Review lib/foo for races"
./grok-exec.sh -T -C /path/to/repo "Parallel research + implement"
./grok-exec.sh -f /tmp/bundle.txt -m grok-4.5 -e high -o json
./grok-exec.sh -w feat-branch -C /path/to/repo "Isolated worktree edit"
Flags: -m · -t · -C · -e effort · -o plain|json|streaming-json · -f · -r (plan + deny write/shell) ·
-s PROFILE · -T native subagent preamble · -w [NAME] worktree · --agents JSON ·
--max-turns · --json-schema · --rules · --disable-web-search · --no-git · -- passthrough.
Default model: grok-4.5 (grok models). No PTY needed — headless -p works on pipes.
-C is absolutized before use.
Native multi-agent
Grok has first-class spawn_subagent (types: general-purpose, explore, plan),
--agents JSON definitions, --no-subagents, --worktree isolation.
-T asks the model to fan out freely and synthesize.
Discipline
- Exit code untrusted — verify results yourself
- Orchestrator owns git (
--no-git) - Long prompts: always
-ffile
Raw surface
See grok --help: permission modes, sandbox, json-schema, tools allow/deny, resume/continue,
grok agent (stdio/headless/serve/leader), worktree, export, doctor.
What ships with it
4 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.
- 3d ago First seen · 49 lines · 88 tokens per session scan A 41c83d03bb8c
grok-cli-agent is a skill published in the GitHub repository ImL1s/agent-cli-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 88 tokens to every session and 607 once invoked, about $0.0004 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-31.
Other skills, from other repositories
search-boost
Multi-engine web search before external API/integration work. Use when verifying versions, SDK signatures, cloud quotas, or comparing libraries. Prefer over built-in searchweb.
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
aria
Designs the data model, API contracts, and structural foundation of the system.
peon-ping-log
Log exercise reps for the Peon Trainer. Use when user says they did pushups, squats, or wants to log reps. Examples - "/peon-ping-log 25 pushups", "/peon-ping-log 30 squats", "log 50 pushups".
agy-delegate
Delegate a coding task to the Google Antigravity CLI (agy) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Antigravity or agy - phrasings like "have Antigravity do X", "delegate this to agy", "run it through agy", or "use…
conductor-implement
Executes the tasks defined in the specified track's plan. Use this to start or continue working on a feature, bug fix, or chore.