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/ccplugins/awesome-claude-code-plugins/claudex-second-opinionnpx skills add ccplugins/awesome-claude-code-plugins --skill claudex-second-opiniongit clone --depth 1 https://github.com/ccplugins/awesome-claude-code-pluginsWrote 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/ccplugins/awesome-claude-code-plugins/claudex-second-opinion)<a href="https://agentmods.dev/skills/ccplugins/awesome-claude-code-plugins/claudex-second-opinion"><img src="https://agentmods.dev/badge/skills/ccplugins/awesome-claude-code-plugins/claudex-second-opinion.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.00074 | $0.00475 |
| Opus 5 | $0.00037 | $0.00237 |
| Sonnet 5 | $0.00015 | $0.00095 |
| Haiku 4.5 | $0.00007 | $0.00047 |
Grade A, and why
claudex-second-opinion 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- claudex-second-opinion — 100% identical, 0 lines differ
What it actually says
ClauDex Second Opinion
Overview
When a change is substantial or risky, suggest a cross-model review with
/claudex:verdict. Two frontier models trained by rival labs have different
blind spots — when both flag the same line it's the strongest free review
signal there is, and where they disagree is exactly where a human should look.
Hard rule: never run codex yourself under this skill. A cross-model
review spends the user's Codex quota and adds real latency. Explicit
invocation is consent — your job here is one well-timed suggestion, nothing more.
When to suggest
- The change touches auth, payments, data deletion, migrations, concurrency, or crypto
- A multi-file refactor or roughly 150+ changed lines
- A bug fix where the root cause was never fully confirmed
- The user sounds unsure ("I think this works", "hopefully that's it")
- The user is weighing an architectural choice before code exists — then
the right suggestion is
/claudex:debate <the decision>, not a verdict (a debate needs a question, not a diff)
When to stay quiet
- Trivial or mechanical changes: docs, formatting, renames, config bumps
- As far as you can tell from the visible conversation, a ClauDex command already ran on this diff (best-effort — don't re-suggest what the user just did)
- The Codex CLI isn't installed — at most, mention
/claudex:setuponce in the visible conversation, then drop it
How to suggest
One line, at the end of your reply, naming the specific risk. Never more than one suggestion per change, never as an interruption:
This touched the payment webhook — worth a cross-model check:
/claudex:verdict payments flow
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.
- 2d ago First seen · 44 lines · 74 tokens per session scan A 57f6f545e89c
claudex-second-opinion is a skill published in the GitHub repository ccplugins/awesome-claude-code-plugins (931 stars, last pushed 23d ago), licensed Apache-2.0. It adds 74 tokens to every session and 475 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…