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/legacybridge-tech/claude-plugins/multi-perspective-analysisnpx skills add legacybridge-tech/claude-plugins --skill multi-perspective-analysisgit clone --depth 1 https://github.com/legacybridge-tech/claude-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/legacybridge-tech/claude-plugins/multi-perspective-analysis)<a href="https://agentmods.dev/skills/legacybridge-tech/claude-plugins/multi-perspective-analysis"><img src="https://agentmods.dev/badge/skills/legacybridge-tech/claude-plugins/multi-perspective-analysis.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.00056 | $0.04158 |
| Opus 5 | $0.00028 | $0.02079 |
| Sonnet 5 | $0.00011 | $0.00832 |
| Haiku 4.5 | $0.00006 | $0.00416 |
Grade A, and why
multi-perspective-analysis 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 3d 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 — 647 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Perspective Analysis Skill
A systematic methodology for examining propositions through dynamically generated expert perspectives.
When to Invoke This Skill
- User presents a proposition, thesis, or idea for examination
- User asks "what do experts think about", "different perspectives on", "analyze this from multiple angles"
- User wants to validate assumptions or find blindspots
- User mentions "devil's advocate", "critique", "challenge this idea"
- User requests debate or contrasting viewpoints
- Keywords: "perspectives", "validate", "blindspots", "assumptions", "debate", "critique", "examine", "multi-angle", "expert opinion"
Core Concepts
Dynamic Expert Generation
Unlike fixed expert panels, this skill generates experts contextually relevant to each proposition:
- Domain Experts (2): Direct specialists in the proposition's field, providing depth
- Adjacent Experts (1-2): Specialists in related but distinct fields, providing breadth
- Contrarian Expert (1): Those likely to challenge the proposition, providing critical perspective
- Meta Expert (1): Methodologists, epistemologists, or systems thinkers, providing macro view
Three Analysis Modes
- Validation Mode: Find blindspots, hidden assumptions, and potential counterarguments
- Comprehensive Analysis Mode: Each expert provides detailed perspective
- Debate Mode: Experts engage in structured dialogue with opposing views
Workflow
Phase 1: Proposition Intake
Extract and clarify the proposition:
- Identify the core claim or thesis
- Detect domain(s) involved (technology, philosophy, business, science, etc.)
- Assess complexity level (simple assertion vs. multi-faceted thesis)
- Note any implicit assumptions visible in the framing
Present understanding to user:
I understand your proposition as:
"[Restate the proposition in clear language]"
Related domains: [Domain 1], [Domain 2], [Domain 3]
Implicit assumptions: [Assumptions built into the proposition]
Is this understanding correct? Would you like to adjust this framing before we continue?
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.
- 3d ago First seen · 647 lines · 56 tokens per session scan A 49b6f369032e
multi-perspective-analysis is a skill published in the GitHub repository legacybridge-tech/claude-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 4,158 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
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…