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 commands/moore-developers/grok-cli/updategit clone --depth 1 https://github.com/Moore-developers/grok-cliWhat 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.00000 | $0.00624 |
| Opus 5 | $0.00000 | $0.00312 |
| Sonnet 5 | $0.00000 | $0.00125 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
update 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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
grok-cli update
Purpose
Check the latest GitHub Release and update the local grok-cli binary when a newer version is available.
The CLI also performs a low-frequency passive update check after human-readable commands. Passive notices are written to stderr and are skipped for --json, --raw-stream, non-interactive output, and the update command itself.
Update settings are stored in:
~/.grok-cli/update.json
Common Usage
Check without installing:
grok-cli update --check
Check and install when a newer release exists:
grok-cli update
Disable passive update notices:
grok-cli update --no-update-check
Re-enable passive update notices:
grok-cli update --enable-update-check
Script or skill usage:
grok-cli update --check --json
Temporarily disable passive checks for a single command:
GROK_CLI_NO_UPDATE_CHECK=1 grok-cli chat "Hello"
Parameters
--json: use the standard JSON envelope.--check: only check the latest release; do not install anything.--force: reinstall the latest release even when the current version already matches it.--no-update-check: persistently disable passive background update notices.--enable-update-check: persistently re-enable passive background update notices.
--check, --force, --no-update-check, and --enable-update-check are mutually exclusive.
Install Strategy
The active update command follows the same distribution policy as installation:
- macOS Apple Silicon downloads
grok-cli-macos-aarch64-apple-darwin.tar.gzand verifies the matching.sha256. - Windows x64 downloads
grok-cli-windows-x86_64-pc-windows-msvc.zip, verifies the matching.sha256, and starts a PowerShell updater because Windows cannot reliably overwrite a running executable. - macOS Intel, Linux, and other source-first platforms run
cargo install --git https://github.com/Moore-developers/grok-cli.git --tag <LATEST_TAG> --locked --force.
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.
- 2d ago First seen · 99 lines · 0 tokens per session scan A e0725b62a7d4
update is a command published in the GitHub repository Moore-developers/grok-cli (52 stars, last pushed 19d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 624 tokens. 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.