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/peterkrueck/claude-code-development-kit/second-opinion-gemininpx skills add peterkrueck/Claude-Code-Development-Kit --skill second-opinion-geminigit clone --depth 1 https://github.com/peterkrueck/Claude-Code-Development-KitWrote 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/peterkrueck/claude-code-development-kit/second-opinion-gemini)<a href="https://agentmods.dev/skills/peterkrueck/claude-code-development-kit/second-opinion-gemini"><img src="https://agentmods.dev/badge/skills/peterkrueck/claude-code-development-kit/second-opinion-gemini.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.00159 | $0.02150 |
| Opus 5 | $0.00079 | $0.01075 |
| Sonnet 5 | $0.00032 | $0.00430 |
| Haiku 4.5 | $0.00016 | $0.00215 |
Grade A, and why
second-opinion-gemini 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Second Opinion — Gemini (explicit / fallback engine)
Get an independent second opinion from Google's Gemini Pro. This model has a completely different architecture and training from Claude, making it genuinely useful for catching blind spots, validating reasoning on edge cases, or surfacing trade-offs you might miss.
This is NOT the default second-opinion engine. Generic second-opinion requests route to the default second-opinion skill. Use this Gemini skill only when:
- The user explicitly asks for Gemini ("ask Gemini", "Gemini's take", "what does Gemini think").
- The user says "ask both" — run this and the default
second-opinionskill, then synthesize all three views (yours + the default engine's + Gemini's). - The default engine was reported unavailable and the user wants the alternate independent voice.
Gemini has full read access to the project — it can read files, grep code, and explore the codebase. Its project instructions (GEMINI.md) tell it to prime itself on the key docs before answering. You provide the specific question and any focused context; Gemini handles the rest.
Model selection
Pinned to gemini-3.1-pro-preview by default for quality (smaller models give weaker second opinions; not worth the false confidence they create).
When Google deprecates the preview pin — preview models rotate fast — override per-session or globally:
export CLAUDE_SECOND_OPINION_MODEL=gemini-3.2-pro # or whatever the current Pro-tier model is
Every invocation below uses the bash pattern ${CLAUDE_SECOND_OPINION_MODEL:-gemini-3.1-pro-preview} — the env var wins if set, otherwise the pinned default.
Do not fall back to a smaller/older model when the pin breaks. Report unavailability and continue with Claude-only analysis.
Process
Step 1: Prepare the Prompt
Gemini has NO access to your conversation history, but it CAN read project files. Structure your prompt as:
- Scope (optional) — by default Gemini primes on the whole project. If the question is about one module or component, name it so Gemini reads the right files first (e.g., "This is about the auth module" — detect the relevant module from the file paths you've been working in).
- The question — what exactly you want Gemini to weigh in on
- Your current thinking (recommended) — share your position so Gemini can challenge it
- Specific context (if needed) — pipe code snippets or diffs via stdin when the relevant code is scattered or you want to focus attention on specific sections
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 135 lines · 159 tokens per session scan A 82299db4ffbe
second-opinion-gemini is a skill published in the GitHub repository peterkrueck/Claude-Code-Development-Kit (1,381 stars, last pushed 1mo ago), licensed MIT. It adds 159 tokens to every session and 2,150 once invoked, about $0.0008 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…