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/stategit 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.00294 |
| Opus 5 | $0.00000 | $0.00147 |
| Sonnet 5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
state 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 state
Purpose
Inspect a redacted summary of the local OAuth state file. state does not call the xAI network; it only reads local auth.json.
If you only want to know whether the session is currently usable, prefer status. state is mainly for troubleshooting what was saved locally.
Common Usage
grok-cli state
grok-cli state --json
Inspect a custom state file:
grok-cli state --auth-file ./auth.json --json
Parameters
--json: use the standard JSON envelope.--auth-file <PATH>: override the OAuth state file path.
Behavior
stateis a redacted show command. It no longer exposespath,show, orvalidatesubcommands.- The command never prints full token values; it only shows whether tokens exist, whether they are expired, and safe summary fields such as provider, auth mode, base URL, last refresh, and last auth error.
JSON Fields
data contains:
providerauth_modeauth_store_pathbase_urlaccess_token_presentrefresh_token_presentaccess_token_expiringlast_refreshlast_auth_error
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 · 49 lines · 0 tokens per session scan A 822176d8c5be
state 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 294 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.