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/kenmege/codex-claude-companion/setupgit clone --depth 1 https://github.com/Kenmege/codex-claude-companionWrote 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/kenmege/codex-claude-companion/setup)<a href="https://agentmods.dev/commands/kenmege/codex-claude-companion/setup"><img src="https://agentmods.dev/badge/commands/kenmege/codex-claude-companion/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.00012 | $0.00198 |
| Opus 5 | $0.00006 | $0.00099 |
| Sonnet 5 | $0.00002 | $0.00040 |
| Haiku 4.5 | $0.00001 | $0.00020 |
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 4d 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
/claude-review:setup
Preflight
- Prefer the helper binary
codex-claudeif it is available on PATH. - If it is not available, tell the user to install the helper with
npm install -g codex-claude-companionafter npmjs publish, or from a cloned checkout withnpm install -g ..
Plan
Run the helper once in setup mode and report readiness.
Commands
- Preferred:
codex-claude setup <user-arguments>
Useful flags:
--jsonfor machine-parseable readiness output with auth identity redacted.
Verification
Do not invent readiness. Use the helper output only.
Summary
Return the helper stdout verbatim.
Next Steps
If setup is not ready, follow the concrete next steps listed by the helper.
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.
- 4d ago First seen · 38 lines · 12 tokens per session scan A 8f91083e74cd
setup is a command published in the GitHub repository Kenmege/codex-claude-companion (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 12 tokens to every session and 198 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
MIGRATE_DESIGN
Design doc for the migration tool PR. Author: Sol ([email protected]). Co-authored-by: wakesync.
critique-screen
Run all seven visual critiques on a screen and output a prioritised fix list.
plan
Create a structured task-by-task implementation plan for a feature and write it to docs/superpowers/plans/.
diff-script
Compare an MDL script against the project's current state.
toh-help
Display all Toh Framework commands and quick usage guide.
dashboard-session-diff
Show file changes (git diff) for a session by id-prefix. Usage /dashboard:session-diff . Runs locally, no LLM.