researcher

A research agent for systematic investigation with grounded references and self-checking.

In plain words
What is it for?
Use it to research a feature, record findings in project documentation, and maintain research prompts and state files for later implementation work.
Why use it?
It provides a structured way to explore a feature while keeping the research connected to the requested scope and supporting evidence.

Agent

Install

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.

agentmods
npx agentmods add agents/griddynamics/rosetta/researcher
Clone the repo
git clone --depth 1 https://github.com/griddynamics/rosetta
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 307 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00022 $0.00307
Opus 5 $0.00011 $0.00153
Sonnet 5 $0.00004 $0.00061
Haiku 4.5 $0.00002 $0.00031

Measured 2d ago against content hash 6ad98527e8d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 2d 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.

instructions/r2/core/agents/researcher.md · 54 lines

What it actually says

Senior research specialist. Systematic, grounded, accuracy-first deep research with meta-prompting approach.

  • All Rosetta prep steps MUST be FULLY completed, load-context skill loaded and fully executed
  • CONTEXT.md, ARCHITECTURE.md, IMPLEMENTATION.md read
  • Research scope and feature name provided by orchestrator
  1. Confirm research scope from orchestrator input.
  2. Apply research skill.
  3. If scope is unclear or research reveals unexpected complexity, MUST STOP, EXPLAIN REASONS, and LET PARENT decide.

<skills_available>

  • USE SKILL research
  • USE SKILL reasoning

</skills_available>

<output_template>

Research output: docs/<feature>-research.md State tracking: research-state.md in FEATURE TEMP folder Research prompt: research-prompt.md in FEATURE PLAN folder

</output_template>

Changes

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.

  1. 2d ago First seen · 54 lines · 22 tokens per session scan A 6ad98527e8d7

Subscribe to this mod's changes

researcher is an agent published in the GitHub repository griddynamics/rosetta (341 stars, last pushed 4d ago), licensed Apache-2.0. It adds 22 tokens to every session and 307 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.

Related

Other agents, from other repositories

README

Optional subagent role definitions (same format as .claw/agents/). Use this folder if you want Claude Code–style paths or to share agent files with tools that only look under .claude/.

deepelementlab/jupyter-studio · 0 tokens

builder

Turn shot-plan.json into one renderable HyperFrames composition (compositions/index.html). Everything stays in the HF ecosystem — HTML is the source of truth; a single paused GSAP timeline carries all motion; the engine seeks it. Category-specific build rules live in categories/ /module.md; this file is the shared…

calesthio/OpenMontage · 0 tokens

hive-scout

Honey hive subagent. Read-only code locator — finds where symbols, callers, configs, or patterns live across the repo and returns the map to the orchestrator as a compact, id-keyed handoff (Honey Lever 3), not prose. Use when the orchestrator needs to locate code without spending main-context tokens reading files.…

Green-PT/honey-for-devs · 76 tokens

sverklo-explore

Drop-in replacement for Claude Code's built-in Explore subagent. Uses sverklo's hybrid-retrieval MCP tools (BM25 + ONNX embeddings + PageRank, 36 tools) to answer file-discovery and code-search questions with 60% fewer tokens than naive grep. Use this when you need to locate definitions, trace references, understand…

sverklo/sverklo · 96 tokens

t-800-factory-architect

Проектирует спецификацию нового субагента: subagent vs skill vs command vs rule, naming, readonly, model, category, calls/calledBy graph. Use when designing a new agent before any files are written. Readonly design phase only.

Khar-AG/t-800-agent · 60 tokens

test

Give your AI agent n8n superpowers. 537 nodes with full schemas, 7,700+ templates, Git-like sync, and TypeScript workflows.

EtienneLescot/n8n-as-code · not measured