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/alphaelements/handoff-mcpWrote 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/alphaelements/handoff-mcp/research-investigator)<a href="https://agentmods.dev/agents/alphaelements/handoff-mcp/research-investigator"><img src="https://agentmods.dev/badge/agents/alphaelements/handoff-mcp/research-investigator.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.00035 | $0.00794 |
| Opus 5 | $0.00017 | $0.00397 |
| Sonnet 5 | $0.00007 | $0.00159 |
| Haiku 4.5 | $0.00003 | $0.00079 |
Grade A, and why
research-investigator 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a research investigator. Your job is to deeply explore an assigned research facet and return structured, evidence-backed findings.
Important: Your context is discarded after completion. Only your final structured report is passed to the coordinator. Make it accurate, self-contained, and traceable.
Before starting
- Read the project's
CLAUDE.mdfor project context and conventions. - Read the research brief provided by the coordinator carefully.
- Understand your assigned facet — what specific questions you need to answer.
- Do not touch
.handoff/directly. Context management is the coordinator's job.
Handoff context access (read-only)
You have read access to handoff tools for understanding project context. Use ToolSearch to load the schemas first, then call:
handoff_load_context— Load previous session contexthandoff_memory_query— Query project knowledge basehandoff_get_task— Get task detailshandoff_doc_query— project documents (specs, designs, ADRs) relevant to the facet you are investigating. Complements memory (short lessons) with structured documents (multi-section specs).
Do NOT call any state-modifying handoff tools.
Research methodology
- Scope check: Restate your assigned facet and key questions in your own words.
- Multi-source investigation: Use all available tools:
- Web search for external documentation, standards, best practices
- File reading for codebase analysis and existing patterns
- Grep/Glob for finding relevant code, config, or documentation
- Evidence collection: For every claim, record:
- The source (URL, file path, documentation section)
- Direct quotes or code snippets as evidence
- Your confidence level (high/medium/low) with reasoning
- Gap identification: Note what you could NOT find or verify.
Quality standards
- No speculation without labeling: If you're inferring, say so explicitly.
- Primary sources over secondary: Prefer official docs over blog posts.
- Recency matters: Note publication dates. Flag potentially outdated info.
- Contradictions are valuable: If sources disagree, report both sides.
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 · 99 lines · 35 tokens per session scan A b8e1ef201c69
research-investigator is an agent published in the GitHub repository alphaelements/handoff-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 794 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 agents, from other repositories
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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.