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 instructions/nguyenvanduocit/research-kit/agents-mdgit 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/instructions/nguyenvanduocit/research-kit/agents-md)<a href="https://agentmods.dev/instructions/nguyenvanduocit/research-kit/agents-md"><img src="https://agentmods.dev/badge/instructions/nguyenvanduocit/research-kit/agents-md.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.03929 | $0.03929 |
| Opus 5 | $0.01965 | $0.01965 |
| Sonnet 5 | $0.00786 | $0.00786 |
| Haiku 4.5 | $0.00393 | $0.00393 |
Grade A, and why
research-kit AGENTS.md 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 5d 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 — 493 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
About Research Kit and Research CLI
Research Kit is a comprehensive toolkit for implementing Systematic Research Development (SRD) - a methodology that emphasizes structured research processes from definition through publication. The toolkit includes templates, scripts, and workflows that guide research teams through a systematic approach to conducting academic and professional research.
Research CLI is the command-line interface that bootstraps research projects with the Research Kit framework. It sets up the necessary directory structures, templates, and AI agent integrations to support the Systematic Research Development workflow.
The toolkit supports multiple AI research assistants, allowing teams to use their preferred tools while maintaining consistent project structure and research practices.
Research Kit Agents
Research Kit includes custom agents that provide autonomous, multi-step research workflows. These agents work alongside slash commands to offer different interaction patterns.
Agents vs Slash Commands
| Aspect | Agents | Slash Commands |
|---|---|---|
| Location | .claude/agents/ |
.claude/commands/, .codex/prompts/ |
| Context | Isolated (own conversation) | Shared (main conversation) |
| Invocation | @agent-name mentions |
Manual with / prefix |
| Use Case | Complex multi-step workflows | Single-step utilities |
| State | Maintains own context | Inline in main thread |
Available Agents
All agents use the agent- prefix in their names:
| Agent | Description | Best For |
|---|---|---|
| agent-research-assistant | Full SRD workflow orchestrator | Starting new research, guided workflow |
| agent-research-reviewer | Quality assurance specialist | Validating definitions, checking rigor |
| agent-literature-specialist | Literature review expert | Systematic source discovery, evaluation, synthesis |
| agent-analysis-expert | Data analysis specialist | Statistical analysis, visualization, pattern discovery |
| agent-data-collector | Data collection specialist | Web scraping, API integration, data gathering |
| agent-academic-writer | Academic writing specialist | Publication-ready outputs, citation management |
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.
- 5d ago First seen · 493 lines · 3,929 tokens per session scan A 64a8bd270afa
research-kit AGENTS.md is an instructions file published in the GitHub repository nguyenvanduocit/research-kit (20 stars, last pushed 5mo ago), licensed MIT. It adds 3,929 tokens to every session, about $0.0196 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.