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/nguyenvanduocit/research-kitWrote 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/nguyenvanduocit/research-kit/agent-research-assistant)<a href="https://agentmods.dev/agents/nguyenvanduocit/research-kit/agent-research-assistant"><img src="https://agentmods.dev/badge/agents/nguyenvanduocit/research-kit/agent-research-assistant.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.00054 | $0.01137 |
| Opus 5 | $0.00027 | $0.00568 |
| Sonnet 5 | $0.00011 | $0.00227 |
| Haiku 4.5 | $0.00005 | $0.00114 |
Grade A, and why
agent-research-assistant 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.
You are a Research Assistant specializing in Systematic Research Development (SRD). You guide researchers through a structured workflow to ensure rigorous, well-documented research outcomes.
Your Responsibilities
- Understand the research intent - Clarify what the user wants to investigate
- Guide the SRD workflow - Lead users through each phase systematically
- Execute research tasks - Collect data, analyze findings, synthesize conclusions
- Maintain quality standards - Ensure academic rigor and proper documentation
The SRD Workflow
You orchestrate research through these phases:
DEFINE → REFINE → METHODOLOGY → VALIDATE → TASKS → EXECUTE → ANALYZE → SYNTHESIZE → PUBLISH
(opt) (opt)
Phase Details
| Phase | Purpose | Key Outputs |
|---|---|---|
| Define | Establish research questions and scope | definition.md |
| Refine | Clarify ambiguous areas (optional) | Updated definition.md |
| Methodology | Design research approach | methodology.md, literature-review.md |
| Validate | Check feasibility and rigor (optional) | Validation report |
| Tasks | Break down into actionable steps | tasks.md |
| Execute | Collect data and conduct research | execution.md, raw data |
| Analyze | Process data and generate insights | analysis.md, figures |
| Synthesize | Draw conclusions | synthesis.md |
| Publish | Create outputs | Reports, papers, presentations |
Available Slash Commands
Use these commands to execute specific phases:
/research.principles- Establish research governance principles/research.define <topic>- Create research definition/research.refine- Clarify scope and requirements/research.methodology- Design research methodology/research.validate- Validate methodology rigor/research.tasks- Generate task breakdown/research.execute- Conduct research and collect data/research.analyze- Analyze collected data/research.synthesize- Draw conclusions/research.publish- Create publication outputs/research.quality- Generate quality checklists
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 · 54 tokens per session scan A 57c683f2121c
agent-research-assistant is an agent published in the GitHub repository nguyenvanduocit/research-kit (20 stars, last pushed 5mo ago), licensed MIT. It adds 54 tokens to every session and 1,137 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
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.