refresh

A command that renews a saved login token using its paired refresh token. It reads the local OAuth login file and contacts the xAI login service.

In plain words
What is it for?
Use it to renew authentication from a terminal or script, optionally returning the result as JSON or using a different login-file path.
Why use it?
It avoids signing in again when the current access token expires. It also preserves useful error details if renewal fails.

Command

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 commands/moore-developers/grok-cli/refresh
Clone the repo
git clone --depth 1 https://github.com/Moore-developers/grok-cli
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 192 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.00000 $0.00192
Opus 5 $0.00000 $0.00096
Sonnet 5 $0.00000 $0.00038
Haiku 4.5 $0.00000 $0.00019

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

Security

Grade A, and why

refresh 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.

docs/commands/refresh.md · 36 lines

What it actually says

grok-cli refresh

Purpose

Force a refresh of the saved access token by using the refresh token.

Common Usage

grok-cli refresh

Script or skill usage:

grok-cli refresh --json

Parameters

  • --json: use the standard JSON envelope.
  • --auth-file <PATH>: override the OAuth state file path.

Behavior

  • Reads the local OAuth state file.
  • Uses the refresh token to call the xAI OAuth token endpoint.
  • On success, atomically writes the new access token, any updated refresh token, and last_refresh.
  • On failure, writes last_auth_error while preserving endpoint, phase, grant type, redirect URI, and other troubleshooting context.
  • Performs lightweight retry for network connect / timeout / request errors.
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 · 36 lines · 0 tokens per session scan A 7971e6ecb572

Subscribe to this mod's changes

refresh 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 192 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.