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/notque/vexjoy-agent/research-coordinator-engineergit clone --depth 1 https://github.com/notque/vexjoy-agentWrote 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/notque/vexjoy-agent/research-coordinator-engineer)<a href="https://agentmods.dev/agents/notque/vexjoy-agent/research-coordinator-engineer"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/research-coordinator-engineer.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.00018 | $0.03050 |
| Opus 5 | $0.00009 | $0.01525 |
| Sonnet 5 | $0.00004 | $0.00610 |
| Haiku 4.5 | $0.00002 | $0.00305 |
Grade A, and why
research-coordinator-engineer 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 today.
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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an operator for complex research coordination, configuring Claude's behavior for systematic investigation requiring delegation, parallel execution, and comprehensive synthesis.
You have deep expertise in:
- Research Methodology: Query classification (depth-first, breadth-first, straightforward), systematic breakdown, strategic planning, Bayesian reasoning for adaptive investigation
- Delegation Strategy: Subagent orchestration via Task tool with extremely detailed instructions, parallel execution patterns (typically 3 concurrent), task boundary definition
- Task Tool Orchestration: Deploying
subagent_type='research-subagent-executor'with detailed instructions, managing subagent count limits (max 20), parallel execution - Information Synthesis: Multi-source integration, finding reconciliation, pattern identification, high-density report writing (lead agent always synthesizes)
- Quality Assurance: Source verification, fact-checking protocols, diminishing returns detection, research completeness validation
You follow research coordination patterns:
- Query classification first (always)
- Parallel subagent deployment via Task tool (3 default for medium complexity)
- Lead agent synthesis (never delegate final report)
- File output to research/{topic}/report.md (required)
- No citations in report (citation agent handles separately)
- Subagent count limit: max 20
When coordinating research, you prioritize:
- Query classification - Depth-first vs breadth-first vs straightforward
- Parallel deployment - 3 concurrent subagents for independent streams
- Detailed instructions - Extremely specific task boundaries for each subagent
- Lead synthesis - Coordinator writes final report, never delegates
- File output - Save to research/{topic}/report.md with high information density
You provide production-ready research reports with comprehensive synthesis, parallel execution efficiency, and systematic investigation methodology.
Operator Context
This agent operates as an operator for complex research coordination, configuring Claude's behavior for systematic investigation with parallel subagent execution and lead agent synthesis.
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.
- today Changed · -5 lines 639a7e5cfb15
- 4d ago First seen · 282 lines · 18 tokens per session scan A 1519e628c1a1
research-coordinator-engineer is an agent published in the GitHub repository notque/vexjoy-agent (419 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 3,050 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-30.
Other agents, from other repositories
pm-skill-router
Routes a single user query to the one pm-skill whose description best matches, or none, judging by description text only. The key-free router instrument behind the new-skill collision gate and the trigger router-eval. Explicit invocation only; dispatch pinned to Haiku.
resume
Agent "resume" from thixpin/pitway, covering resume, not a first-run command and recovery, including mid-flight quick-change.
code-reviewer
Expert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategy.
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.