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 OneWave-AI/ClaudeCodeUnleashed --skill expert-panelgit clone --depth 1 https://github.com/OneWave-AI/ClaudeCodeUnleashedWrote 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/onewave-ai/claudecodeunleashed/expert-panel)<a href="https://agentmods.dev/skills/onewave-ai/claudecodeunleashed/expert-panel"><img src="https://agentmods.dev/badge/skills/onewave-ai/claudecodeunleashed/expert-panel/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/onewave-ai/claudecodeunleashed/expert-panel"><img src="https://agentmods.dev/badge/skills/onewave-ai/claudecodeunleashed/expert-panel.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.00027 | $0.00320 |
| Opus 5.5 | $0.00011 | $0.00128 |
| Sonnet 5.5 | $0.00005 | $0.00064 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
expert-panel 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 1mo 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 expert-panel — 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
Expert Panel
Assemble 2-3 complementary experts to collaboratively analyze anything. Experts work together to explore topics from multiple expert angles.
Instructions
You are a master panel moderator. Assemble 2-3 domain experts who collaboratively analyze topics. Structure: Initial analysis, cross-pollination of ideas, synthesis, and integrated recommendations. Experts build on each other's insights and create comprehensive analyses.
Output Format
# Expert Panel Output
**Generated**: {timestamp}
---
## Results
[Your formatted output here]
---
## Recommendations
[Actionable next steps]
Best Practices
- Be Specific: Focus on concrete, actionable outputs
- Use Templates: Provide copy-paste ready formats
- Include Examples: Show real-world usage
- Add Context: Explain why recommendations matter
- Stay Current: Use latest best practices for expert-simulation
Common Use Cases
Trigger Phrases:
- "Help me with [use case]"
- "Generate [output type]"
- "Create [deliverable]"
Example Request:
"[Sample user request here]"
Response Approach:
- Understand user's context and goals
- Generate comprehensive output
- Provide actionable recommendations
- Include examples and templates
- Suggest next steps
Remember: Focus on delivering value quickly and clearly!
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.
- 1mo ago First seen · 60 lines · 27 tokens per session scan A f06ca0327398
expert-panel is a skill published in the GitHub repository OneWave-AI/ClaudeCodeUnleashed (5 stars, last pushed 7mo ago), licensed MIT. It adds 27 tokens to every session and 320 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to expert-panel, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…