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 skills/willinvest/claudex/thinknpx skills add WillInvest/ClaudeX --skill thinkgit clone --depth 1 https://github.com/WillInvest/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/skills/willinvest/claudex/think)<a href="https://agentmods.dev/skills/willinvest/claudex/think"><img src="https://agentmods.dev/badge/skills/willinvest/claudex/think.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.00052 | $0.01268 |
| Opus 5 | $0.00026 | $0.00634 |
| Sonnet 5 | $0.00010 | $0.00254 |
| Haiku 4.5 | $0.00005 | $0.00127 |
Grade A, and why
think 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.
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
claudex:think — brainstorming with a Codex second opinion
Brainstorm normally, but every clarifying question is routed through Codex for a second opinion before the user sees it. Enforcement is automatic — you never call Codex yourself, and you do NOT need to run any shell command to turn it on.
How arming works (automatic)
When the user runs /claudex:think, a UserPromptExpansion hook arms the gate for this session automatically (it runs in hook context, so it isn't subject to the permission classifier). You don't touch it.
Steps
-
Brainstorm. Invoke
Skill(superpowers:brainstorming)and follow it normally. Ask clarifying questions viaAskUserQuestionas usual — the hook intercepts each one. -
Handle the Codex critique. When you try to ask a clarifying question, the hook blocks it. The (red) denial reason is kept short on purpose — it points you to a file (
~/.claude/claudex/state/<session>-critique.md) holding your drafted question + Codex's critique, so the critique isn't shown red and then repeated. Read that file, then in ONE message:- Show the question you originally drafted verbatim under an
**Original question:**heading (keep your recommended option), so the user can see your framing before Codex weighed in. - Present Codex's critique verbatim under a
**Codex says:**heading. - Add
**My take:**— 1-3 sentences: do you agree? Fold any fixes you accept into the question. - Re-issue the
AskUserQuestion(revised if you agreed) — the revised question is the one the user actually answers. It passes through this time (one re-issue is allowed within ~2 minutes of the block).
So each round the user sees, in order: Original question (with your recommendation) → Codex says → My take → the answer window — with no red duplicate of the critique. (If the file can't be written, the hook falls back to putting the critique inline in the denial reason.)
- Show the question you originally drafted verbatim under an
-
Wrap up. When you transition to
writing-plans, the gate auto-disarms (aPreToolUseSkill hook handles it); it also auto-expires after the TTL.
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 · 51 lines · 52 tokens per session scan A 88b0b17c78b4
think is a skill published in the GitHub repository WillInvest/ClaudeX (4 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 1,268 once invoked, about $0.0003 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 skills, from other repositories
brainstorming
You MUST use this before any creative work (features, products, content, strategy, systems, or behavior changes). Start by classifying what we’re brainstorming, then run thorough one-question-at-a-time discovery, propose 2–3 approaches, and converge on a validated plan/spec.
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
agui-dotnet-streaming-chat
Get started with the AG-UI .NET SDK: bootstrap and run your first streaming-chat app (client + server) with the AG-UI .NET NuGet packages (AGUI.Client, AGUI.Server, AGUI.Formatting, AGUI.Abstractions). USE FOR: which packages to install and how to wire them; constructing an AGUIChatClient against an endpoint and…
agui-dotnet-sample-step
Add a GettingStarted sample Step (a Server/Client pair) to the AG-UI .NET SDK that demonstrates one protocol feature the way we want users to write it. USE FOR: adding a new samples/GettingStarted/StepNN Server+Client pair, wiring it into AGUI.slnx and the integration-test project, giving it a deterministic…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…