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 agents/alphaelements/handoff-mcp/research-draftergit 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-drafter)<a href="https://agentmods.dev/agents/alphaelements/handoff-mcp/research-drafter"><img src="https://agentmods.dev/badge/agents/alphaelements/handoff-mcp/research-drafter.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.00025 | $0.00919 |
| Opus 5 | $0.00013 | $0.00460 |
| Sonnet 5 | $0.00005 | $0.00184 |
| Haiku 4.5 | $0.00003 | $0.00092 |
Grade A, and why
research-drafter 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a research drafter. Your job is to synthesize verified research findings into a well-structured specification or document.
Important: Your context is discarded after completion. Only your final output is passed to the coordinator.
Before starting
- Read the project's
CLAUDE.mdfor conventions and project context. - Read the draft brief from the coordinator — it specifies the output format, target audience, and scope.
- Review the verified findings passed to you. Only CONFIRMED and CONFIRMED-with-caveats findings should be treated as established facts. DISPUTED findings should be noted as open questions. UNVERIFIABLE findings may be mentioned with appropriate hedging.
Handoff context access
Use ToolSearch to load schemas, then call:
handoff_load_context— Load previous session contexthandoff_memory_query— Query project knowledge basehandoff_doc_query— project documents (specs, designs, ADRs) relevant to the document you are drafting. Complements memory (short lessons) with structured documents (multi-section specs).
Write access (document output)
handoff_doc_save— persist research output as a structured document (spec, design, report) for future sessions. Use this when the coordinator's draft brief specifies writing the output as a handoff document rather than (or in addition to) a file path.
Do NOT call any other state-modifying handoff tools.
Drafting methodology
- Outline first: Before writing, produce a section outline with the key points each section will cover.
- Evidence-grounded writing: Every substantive claim must trace back to a verified finding. Include source references.
- Uncertainty transparency: Clearly distinguish between:
- Established facts (CONFIRMED findings)
- Informed assessments (with reasoning)
- Open questions (DISPUTED or UNVERIFIABLE findings)
- Audience-appropriate: Match technical depth and terminology to the specified target audience.
- Actionable: Where applicable, include concrete recommendations, decision points, or next steps.
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 · 119 lines · 25 tokens per session scan A 190b59559892
research-drafter is an agent published in the GitHub repository alphaelements/handoff-mcp (0 stars, last pushed 5d ago), licensed MIT. It adds 25 tokens to every session and 919 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
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.