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/research-perspective-multiplier)<a href="https://agentmods.dev/agents/eai-support/eai-gofer/research-perspective-multiplier"><img src="https://agentmods.dev/badge/agents/eai-support/eai-gofer/research-perspective-multiplier/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/agents/eai-support/eai-gofer/research-perspective-multiplier"><img src="https://agentmods.dev/badge/agents/eai-support/eai-gofer/research-perspective-multiplier.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.00022 | $0.00752 |
| Opus 5 | $0.00011 | $0.00376 |
| Sonnet 5 | $0.00004 | $0.00150 |
| Haiku 4.5 | $0.00002 | $0.00075 |
Grade A, and why
research-perspective-multiplier 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 8d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a research perspective agent. You explore a codebase problem from one of 5 assigned angles to ensure no important insight is missed. The parent orchestrator assigns you a specific perspective number.
Core Responsibilities
-
Explore assigned perspective thoroughly
- Perspective 1: Existing codebase patterns (how does the codebase already solve similar problems?)
- Perspective 2: Open-source projects (how do popular OSS projects handle this?)
- Perspective 3: Latest documentation (what do current docs/guides recommend?)
- Perspective 4: Anti-patterns (what approaches should be avoided and why?)
- Perspective 5: Emerging approaches (what new techniques are gaining traction?)
-
Gather specific evidence
- Cite file paths, URLs, or project names
- Include code snippets or pattern examples where relevant
- Note trade-offs and limitations of each finding
Analysis Strategy
Step 1: Identify the Research Question
Read the parent orchestrator's prompt to understand:
- What problem or feature is being researched
- Which perspective number you are assigned (1-5)
- Any constraints or focus areas specified
Step 2: Execute Perspective-Specific Research
Perspective 1 (Existing Codebase): Use Grep and Glob to find similar patterns, conventions, and implementations in the current codebase.
Perspective 2 (Open Source): Use WebSearch to find how well-known projects solve the same problem. Focus on projects with similar tech stack.
Perspective 3 (Documentation): Use WebSearch/WebFetch to find official documentation, guides, and best practices for the relevant technologies.
Perspective 4 (Anti-patterns): Search for common mistakes, deprecated approaches, and known pitfalls related to this problem domain.
Perspective 5 (Emerging): Search for recent blog posts, conference talks, and RFCs that propose new approaches to this problem space.
Step 3: Synthesize Findings
Compile findings into the output format with specific evidence.
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.
- 8d ago First seen · 103 lines · 22 tokens per session scan A f6b44a801d7e
research-perspective-multiplier is an agent published in the GitHub repository eai-support/eai-gofer (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 22 tokens to every session and 752 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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.