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.
git clone --depth 1 https://github.com/hamza-ali-shahjahan/claudexWrote 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/hamza-ali-shahjahan/claudex/setup)<a href="https://agentmods.dev/commands/hamza-ali-shahjahan/claudex/setup"><img src="https://agentmods.dev/badge/commands/hamza-ali-shahjahan/claudex/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.1 | $0.00014 | $0.00363 |
| Opus 5 | $0.00007 | $0.00181 |
| Sonnet 5 | $0.00003 | $0.00073 |
| Haiku 4.5 | $0.00001 | $0.00036 |
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 7d 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.
This is a copy
100% identical to setup — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Check each prerequisite and report it as ✅ or ❌ with the exact fix command:
- Codex CLI installed —
codex --version(fix:npm i -g @openai/codex) - Codex authenticated —
codex login statusor the equivalent for the installed version (fix:codex login) - Inside a git repo —
git rev-parse --is-inside-work-tree. Distinguish the two failure modes: git not installed (fix:xcode-select --installon macOS,apt install git/winget install Git.Gitelsewhere) vs. not a repository (fix:git init— ClauDex reviews diffs, so it needs one) - Optional: the official Codex plugin for
/codex:*commands (/plugin marketplace add openai/codex-plugin-cc, then/plugin install codex@openai-codex)
When everything passes, reply:
"ClauDex is ready. Claude writes, Codex reviews, you ship. 🧡🖤
First time? Run /claudex:demo — two minutes, zero risk: watch the two
models argue over planted bugs before you point them at real code."
If the Codex CLI or its login is missing, end with:
"It takes two to ClauDex. 🧡 Claude is here — 🖤 Codex is not. Run the fix
commands above, then /claudex:setup again for the duet."
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.
- 7d ago First seen · 26 lines · 14 tokens per session scan A c57f2e6a7ac1
setup is a command published in the GitHub repository hamza-ali-shahjahan/claudex (4 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 363 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to setup, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
duck-off
Turn off Rubber Duck mode and answer normally.
save
Save the current session digest. Fans out across every writable memory tier per the house-map. Tier 0 always; Tier 1 if reachable; Tier 2 only if registered writable with auth. Each tier independent — failures degrade gracefully.
check-on-claude
Maude checks on Claude — repeated tool calls, unread context, confabulation risk, missed CLAUDE.md, the patterns Claude doesn't see in himself.
notice
Maude surfaces patterns from the turn-by-turn trace — recurring topics, repeated mistakes, time-of-day patterns, sessions that keep ending in the same place.
promote
Show what the tape is holding for your word, and promote the ones you approve into canon. Agent inference never becomes canon on its own — this is the door, and your hand is on it.
help
Rubber Duck: what it does, how to steer it, how to stop it.