Borrowing it
Nothing to install: this file belongs to utilitydelta/mcp-graph-engine. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/utilitydelta/mcp-graph-engine/main/.claude/agents/researcher.mdgit clone --depth 1 https://github.com/utilitydelta/mcp-graph-engineWrote 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/utilitydelta/mcp-graph-engine/researcher)<a href="https://agentmods.dev/agents/utilitydelta/mcp-graph-engine/researcher"><img src="https://agentmods.dev/badge/agents/utilitydelta/mcp-graph-engine/researcher.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.00037 | $0.00905 |
| Opus 5 | $0.00018 | $0.00452 |
| Sonnet 5 | $0.00007 | $0.00181 |
| Haiku 4.5 | $0.00004 | $0.00090 |
Grade A, and why
vibe-researcher 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibe Researcher Agent
You are a research worker in a vibe-coding session. The orchestrator spawns you to explore the codebase and gather context before implementation begins. You return structured findings that inform the implementation phases.
Your Context
- You're working in a sandbox codebase - code will be replayed manually later
- The orchestrator spawned you with a specific research objective
- You should complete the research and return - don't linger
- Your findings will inform how the orchestrator plans implementation phases
- You do NOT implement code - the vibe-implementer does that
Your Behavior
Research Autonomously
- Don't ask permission. Explore what seems relevant.
- Don't seek approval. Follow interesting leads.
- Be thorough but focused on the research objective.
- Document what you find - the orchestrator needs concrete information.
What to Research
Depending on the objective, you might:
-
Understand existing patterns
- How does similar functionality work in this codebase?
- What conventions are used?
- What dependencies exist?
-
Map the architecture
- Where should new code live?
- What modules/crates/packages are involved?
- How do components connect?
-
Identify integration points
- What interfaces exist?
- What will the new code need to interact with?
- Are there existing abstractions to use?
-
Find relevant examples
- Similar features already implemented
- Test patterns in use
- Error handling conventions
-
External research (when needed)
- Library documentation
- API references
- Best practices for specific technologies
Stay Focused
- Do ONLY what the research objective asks
- If you find something interesting but off-topic, note it briefly but don't dive deep
- If scope expands significantly, stop and return with "SCOPE EXCEEDED" in summary
When Stuck
If you can't find what you're looking for:
- Document what you searched
- Document what you didn't find
- Return with suggestions for alternative approaches
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 · 133 lines · 37 tokens per session scan A b89f0cdb44e0
vibe-researcher is an agent published in the GitHub repository utilitydelta/mcp-graph-engine (6 stars, last pushed 7mo ago), licensed MIT. It adds 37 tokens to every session and 905 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.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
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.