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 skills add HawkannG/Claude-Warden --skill warden-second-opiniongit clone --depth 1 https://github.com/HawkannG/Claude-WardenWrote 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/hawkanng/claude-warden/warden-second-opinion)<a href="https://agentmods.dev/skills/hawkanng/claude-warden/warden-second-opinion"><img src="https://agentmods.dev/badge/skills/hawkanng/claude-warden/warden-second-opinion/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hawkanng/claude-warden/warden-second-opinion"><img src="https://agentmods.dev/badge/skills/hawkanng/claude-warden/warden-second-opinion.svg" alt="Reviewed on agentmods" width="80" 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.00030 | $0.01998 |
| Opus 5 | $0.00015 | $0.00999 |
| Sonnet 5 | $0.00006 | $0.00400 |
| Haiku 4.5 | $0.00003 | $0.00200 |
Grade A, and why
warden-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 11d 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Second Opinion Protocol
Policy Area: WORKFLOW Version: 1.0 Status: Active Enforcement: Tier 1 SHOULD, Tier 2 MUST (per RFC 2119) Purpose: When Claude is stuck in a loop of failed fixes, spawn a fresh subagent with no context baggage to diagnose the root cause. Two tiers escalate from voluntary self-check to mandatory human handoff.
1. Overview
The Second Opinion protocol breaks the cycle of compounding failed fixes by bringing in fresh perspective. Instead of continuing to guess, Claude spawns a separate agent that reads the code without inherited assumptions and delivers an independent diagnosis.
Two tiers exist:
| Tier | Trigger | Nature | Outcome |
|---|---|---|---|
| Tier 1 | 3 edits to same file, or manual | Voluntary (SHOULD) | Structured diagnosis, Claude acts on it |
| Tier 2 | 5 edits to same file | Mandatory (MUST) | Deep diagnosis + human-pasteable summary, Claude STOPS |
2. Tier 1: Structured Thinking Partner
2.1 When It Triggers
- Automatic: Claude has edited the same file 3 times to fix the same issue, OR
- Manual: Human invokes
/second-opinion, OR Claude recognizes it is going in circles
Tier 1 is a SHOULD — Claude is expected to use it but may justify skipping if the situation is genuinely different on each attempt.
2.2 Step 1: Prepare the Problem Brief
Claude prepares a structured brief containing ONLY facts, not theories:
PROBLEM BRIEF
Goal: [What we are trying to accomplish]
What I've tried:
1. [Approach] → [Result]
2. [Approach] → [Result]
3. [Approach] → [Result]
Current error: [Exact error message or incorrect behavior]
Assumptions I'm making:
- [Assumption 1]
- [Assumption 2]
Key files:
- [path/to/file] — [role in the problem]
- [path/to/file] — [role in the problem]
2.3 Step 2: Spawn the Subagent
Spawn a Task agent with the following parameters:
subagent_type:general-purpose- Description:
Second opinion: diagnose [brief description of issue] - Prompt:
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.
- 11d ago First seen · 244 lines · 30 tokens per session scan A 3d013c5e3284
warden-second-opinion is a skill published in the GitHub repository HawkannG/Claude-Warden (2 stars, last pushed 6mo ago), licensed MIT. It adds 30 tokens to every session and 1,998 once invoked, about $0.0002 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
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
argus
Argus — the all-seeing scanner suite. Six automated scanners for high-value web + LLM bug classes — CORS misconfiguration (origin reflection / null / credentialed read), CRLF & host-header injection, NoSQL injection (operator auth-bypass / $where blind), JWT attacks (alg:none / RS256→HS256 confusion / secret crack)…
investigate
Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively invoke this skill (do NOT debug…
hns-lsel-curator
Local Self-Evolution Loop (LSEL) curator — the CLUSTER + drain engine for the GOOS-local PROPOSE→APPLY seam closure (SPEC-LSEL-LOCAL-EVOLUTION-001). Companion-offset drain of .moai/lessons-inbox.jsonl with a drain-side severity filter that drops the 65% Bash-timeout/sandbox noise, eventkey clustering with a frequency…
cherry-assistant-guide
A guide for looking up Cherry Studio's product details and diagnosing problems such as connection failures, setup errors, and runtime issues.
cherry-electron-dev
Develop, fix, and profile Cherry Studio in a tracked Electron instance. Use for everyday implementation, UI and interaction work, bug fixing, runtime debugging, DevTools inspection, lag or jank investigation, CPU and memory monitoring, leak checks, and startup-performance analysis; reuse a verified workspace instance…