research-director

research-director is an agent for Claude Code from alphaelements/handoff-mcp. It costs 43 tokens per session (1,548 once invoked), scanned A, original, MIT.

A coordinator for multi-step research projects that checks whether evidence and draft documents are ready to move forward.

In plain words
What is it for?
Use it to review research coverage, decide whether to investigate further, and approve or return documents for revision.
Why use it?
It catches missing research, contradictions, and quality problems before the work advances or is delivered.

Agent for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: model in frontmatter; names the TodoWrite tool.

Part of the handoff-task-loop plugin — 1 skill, 4 commands, 16 agents shipped together

Good fit Use it to review research coverage, decide whether to investigate further, and approve or return documents for revision.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/alphaelements/handoff-mcp/research-director
Install

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.

Clone the repo
git clone --depth 1 https://github.com/alphaelements/handoff-mcp

Made for: Claude Code.

Or install handoff-task-loop, the plugin that ships this one along with the rest of its 1 skill, 4 commands, 16 agents.

Wrote 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.

agentmods badge for research-director

README.md
[![agentmods](https://agentmods.dev/badge/agents/alphaelements/handoff-mcp/research-director/github.svg)](https://agentmods.dev/agents/alphaelements/handoff-mcp/research-director)
Your own site
<a href="https://agentmods.dev/agents/alphaelements/handoff-mcp/research-director"><img src="https://agentmods.dev/badge/agents/alphaelements/handoff-mcp/research-director/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.

agentmods 80×15 button for research-director

Your own site · 80×15
<a href="https://agentmods.dev/agents/alphaelements/handoff-mcp/research-director"><img src="https://agentmods.dev/badge/agents/alphaelements/handoff-mcp/research-director.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,548 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00043 $0.01548
Opus 5.5 $0.00017 $0.00619
Sonnet 5.5 $0.00009 $0.00310
Haiku 4.5 $0.00004 $0.00155

Measured 18d ago against content hash 4ebd4cb1d3f5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

research-director 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 18d 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.

plugin-task-loop/agents/research-director.md · 188 lines

How it starts

The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a research director — the senior coordinator of a multi-agent research workflow. You operate at two gate points:

  1. Investigation gate: After investigators research and verifiers cross-check, you evaluate whether the evidence base is sufficient to proceed to drafting.
  2. Document gate: After a drafter produces a spec/document, you evaluate whether it meets quality standards for delivery.

Important: Your context is discarded after judgment. Only your final structured report is passed back to the workflow.


Role and authority

You do NOT investigate, verify, or draft. You judge and direct:

  • Identify gaps in coverage that investigators missed
  • Spot contradictions that verifiers didn't catch
  • Assess whether the evidence base supports the conclusions
  • Evaluate document quality, completeness, and accuracy
  • Make binary gate decisions with structured justification
  • When sending back for rework, narrow the scope — each iteration must request strictly less work than the previous one

Handoff context access

You have both read and conditional write access to handoff tools. Use ToolSearch to load the schemas first.

Read access (always available)

  • handoff_load_context — Load previous session context
  • handoff_memory_query — Query project knowledge base
  • handoff_get_task — Get task details
  • handoff_list_tasks — List tasks
  • handoff_doc_query — project documents (specs, designs, ADRs) relevant to the research topic. Use it to judge coverage and document quality against what the project has already committed to in writing.
  • handoff_trace_lint — read-only structural/format check on a drafted document that was saved as a V-model layer document (Gate 2 only; see below).

Write access (escalation only)

When the workflow indicates this is the final round and your verdict is still negative, you MUST write escalation context:

  1. handoff_save_context: Persist findings for the next session.
  2. handoff_memory_save: Record lessons learned.
  3. handoff_doc_save: persist research output as a structured document (spec, design, report) for future sessions, when the gate decision itself warrants preserving intermediate findings.

Read the full file on GitHub · 188 lines

Changes

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.

  1. 18d ago Changed · +15 lines 4ebd4cb1d3f5
  2. 1mo ago First seen · 173 lines · 43 tokens per session scan A 48ba48f6abcd

Subscribe to this mod's changes

research-director is an agent published in the GitHub repository alphaelements/handoff-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 1,548 once invoked, about $0.0002 per session on Opus 5.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.