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/modelgit 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.00439 |
| Opus 5 | $0.00000 | $0.00219 |
| Sonnet 5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
model 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.
What it actually says
grok-cli model
Purpose
Inspect and choose the shared default model for text commands. chat and search share the same default, so changing it once affects both.
grok-cli mode is an alias for grok-cli model.
Common Usage
Interactive selection:
grok-cli model
grok-cli mode
In an interactive terminal, the command shows the following list and supports arrow-key navigation:
grok-4.5
grok-4.6
exit
After selection, it prints:
Model switched to <MODEL>.
Script or skill lookup:
grok-cli model --json
Script or skill direct selection:
grok-cli model --json --model grok-4.6
Parameters
--json: use the standard JSON envelope; this skips interactive selection.--auth-file <PATH>: override the OAuth state file path.--model <MODEL>: save the shared default model forchatandsearch.
Behavior
grok-cli modelneeds a readable auth state.- It no longer exposes
show,list, orsetsubcommands. - Without
--model, interactive terminals open the arrow-key selection UI; non-interactive environments print the current selection and model catalog. - With
--model, the shared text model is written toauth.jsonmetadata. --commandand--taskare preserved only as hidden compatibility parameters. Public behavior always keepschatandsearchon the same model.- Media commands should pass
--modeldirectly on their own command line if they need a model override.
JSON Fields
Lookup mode data contains:
providerselected_modelselectedcatalog
Set mode data contains:
providermodelselectedcatalog
Related Docs
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 · 79 lines · 0 tokens per session scan A c260e354c24d
model 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 439 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.