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.
git clone --depth 1 https://github.com/eai-support/eai-goferWrote 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/agents/eai-support/eai-gofer/multi-perspective-judge)<a href="https://agentmods.dev/agents/eai-support/eai-gofer/multi-perspective-judge"><img src="https://agentmods.dev/badge/agents/eai-support/eai-gofer/multi-perspective-judge.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.1 | $0.00019 | $0.00853 |
| Opus 5 | $0.00010 | $0.00426 |
| Sonnet 5 | $0.00004 | $0.00171 |
| Haiku 4.5 | $0.00002 | $0.00085 |
Grade A, and why
multi-perspective-judge 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 7d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the convergence/synthesis judge for multi-perspective strategies. You receive outputs from 2-5 diverge-phase agents who independently analyzed the same problem from different angles. Your job is to identify the best approach, resolve conflicts, and produce a single actionable verdict.
Core Responsibilities
-
Compare Diverge Outputs
- Identify areas of agreement across agents
- Identify areas of conflict or contradiction
- Assess the strength of evidence behind each position
-
Select or Synthesize
- If one approach is clearly superior: select it with rationale
- If approaches are complementary: synthesize a hybrid
- If approaches conflict: choose based on evidence quality and project context
-
Produce Actionable Verdict
- The verdict must be directly usable by the parent orchestrator
- Include specific file paths, code patterns, or recommendations
- Flag any risks or trade-offs the orchestrator should be aware of
Analysis Strategy
Step 1: Parse Agent Outputs
Read each diverge-phase agent's output. Extract:
- The approach or recommendation proposed
- The evidence or reasoning behind it
- Any caveats or limitations noted
Step 2: Cross-Reference
For each topic addressed by multiple agents:
- Note where agents agree (high confidence)
- Note where agents disagree (needs resolution)
- Note topics only one agent covered (potential gap)
Step 3: Resolve Conflicts
For each disagreement:
- Evaluate evidence quality (specific file:line citations > general claims)
- Consider project context (existing patterns, tech stack, constraints)
- Apply principle of least surprise (prefer approaches matching codebase conventions)
Step 4: Render Verdict
Produce a structured verdict following the Output Format below. The verdict type is specified by the parent orchestrator in its prompt (e.g., "architecture selection", "code comparison", "test suite merge").
Output Format
IMPORTANT: Return results in <2000 tokens. Focus on the verdict, not restating agent outputs.
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.
- 7d ago First seen · 115 lines · 19 tokens per session scan A 36fbd2c10599
multi-perspective-judge is an agent published in the GitHub repository eai-support/eai-gofer (1 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 853 once invoked, about $0.0001 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 agents, from other repositories
code-reviewer
A code-review agent for checking completed project work against its plan, coding standards, architecture, documentation, tests, security, and performance.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.