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/haenara-shin/codex-hud/setup-keygit clone --depth 1 https://github.com/haenara-shin/codex-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/haenara-shin/codex-hud/setup-key)<a href="https://agentmods.dev/commands/haenara-shin/codex-hud/setup-key"><img src="https://agentmods.dev/badge/commands/haenara-shin/codex-hud/setup-key.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.00022 | $0.00449 |
| Opus 5 | $0.00011 | $0.00225 |
| Sonnet 5 | $0.00004 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
setup-key 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 5d 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
Configure OpenAI Admin API Key
This command is only needed for dollar-cost tracking via /codex-hud:costs-today/week/month. Rate limits, token usage, and the statusline work without it.
First, check the current state:
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" setup --json
If "status": "connected", tell the user the key is already configured and working. Offer to replace it (optional).
If "status": "no_key" or the user wants to replace the key:
IMPORTANT — never ask the user to paste the key into the chat. Anything typed into the conversation is stored in session transcripts. Use the clipboard instead.
Tell the user:
- Open https://platform.openai.com/settings/organization/admin-keys
- Create or copy an Admin key (starts with
sk-admin-...) — leave it in the clipboard
Then ask via AskUserQuestion:
- header: "Admin Key"
- question: "Is the Admin API key copied to your clipboard? (It will be read directly from the clipboard — never typed into the chat.)"
- multiSelect: false
- options:
- "Key is in my clipboard" — proceed
- "Cancel" — abort without changes
If the user confirms, read the key from the clipboard and pipe it via stdin (macOS; on Linux substitute wl-paste or xclip -selection clipboard -o):
pbpaste | node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" setup --key-stdin --json
On success ("status": "saved"), tell the user it was saved and verified, and suggest clearing the clipboard:
printf '' | pbcopy
On failure, show the error and suggest they re-copy the key from the URL above and try again.
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.
- 5d ago First seen · 49 lines · 22 tokens per session scan A 2ec3cccc4649
setup-key is a command published in the GitHub repository haenara-shin/codex-hud (8 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 449 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
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.