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/xiyoumc/grok-hud/setupgit clone --depth 1 https://github.com/xiyouMc/grok-hudWrote 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/commands/xiyoumc/grok-hud/setup)<a href="https://agentmods.dev/commands/xiyoumc/grok-hud/setup"><img src="https://agentmods.dev/badge/commands/xiyoumc/grok-hud/setup.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.00019 | $0.00499 |
| Opus 5 | $0.00010 | $0.00249 |
| Sonnet 5 | $0.00004 | $0.00100 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
setup 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-hud:setup
Install the grok-hud CLI so you can watch Grok context usage outside the TUI (Grok has no native statusline API).
Arguments
$ARGUMENTS
--link— also runnpm linksogrok-hudis on PATH
Steps (run them)
-
Resolve plugin root:
- Prefer env
GROK_PLUGIN_ROOTif set - Else use the directory that contains this plugin's
package.json/bin/grok-hud.js
- Prefer env
-
Build:
PLUGIN_ROOT="${GROK_PLUGIN_ROOT:-$(pwd)}"
# If not already in the plugin dir, locate it:
# grok plugin details grok-hud
cd "$PLUGIN_ROOT"
npm install
npm run build
chmod +x bin/grok-hud.js
- Write default config (idempotent):
node bin/grok-hud.js --init-config
- If user passed
--link(or asked for global install):
npm link
- Smoke test:
node bin/grok-hud.js --once
# or, if linked:
grok-hud --once
- Tell the user next steps:
| Goal | Command |
|---|---|
| One-shot snapshot | grok-hud or /grok-hud:status |
| Live pane | grok-hud --watch or /grok-hud:watch |
| tmux bar | set -g status-right '#(grok-hud --tmux --no-color) | %H:%M' |
| Config | ~/.grok/plugins/grok-hud/config.json or /grok-hud:configure |
Notes
- Data is read-only from
~/.grok/active_sessions.jsonand sessionsignals.json/updates.jsonl. - Inside Grok TUI you can still use
/context,/session-info,/usage. - If
npm/nodeis missing, ask the user to install Node.js ≥ 18 first.
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 · 68 lines · 19 tokens per session scan A 01432498b12f
setup is a command published in the GitHub repository xiyouMc/grok-hud (8 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 499 once invoked, about $0.0001 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.