agentmods.dev

research-flow

research-flow is a command for Claude Code from griddynamics/rosetta. It costs 17 tokens per session (655 once invoked), scanned A, original, Apache-2.0.

A structured workflow for researching a software project using several exploration steps and supporting references.

In plain words
What is it for?
It is for gathering project information, refining research questions, exploring code or documents, and recording the results.
Why use it?
It turns a broad research request into an organized process with project context, parallel investigation, and saved progress.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: mentions subagents.

not rated 363repo +3 changed 13d ago A scan 17 tokens original Apache-2.0

Good fit It is for gathering project information, refining research questions, exploring code or documents, and recording the results.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/griddynamics/rosetta/research-flow
View source ↗ griddynamics/rosetta griddynamics.github.io
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.

Clone the repo
git clone --depth 1 https://github.com/griddynamics/rosetta

Made for: Claude Code.

Wrote 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.

agentmods badge for research-flow

README.md
[![agentmods](https://agentmods.dev/badge/commands/griddynamics/rosetta/research-flow/github.svg)](https://agentmods.dev/commands/griddynamics/rosetta/research-flow)
Your own site
<a href="https://agentmods.dev/commands/griddynamics/rosetta/research-flow"><img src="https://agentmods.dev/badge/commands/griddynamics/rosetta/research-flow/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for research-flow

Your own site · 80×15
<a href="https://agentmods.dev/commands/griddynamics/rosetta/research-flow"><img src="https://agentmods.dev/badge/commands/griddynamics/rosetta/research-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 655 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00017 $0.00655
Opus 5.5 $0.00007 $0.00262
Sonnet 5.5 $0.00003 $0.00131
Haiku 4.5 $0.00002 $0.00065

Measured 13d ago against content hash 32c066fbb4f8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

research-flow 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 13d 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.

plugins/core-copilot-light/commands/research-flow.md · 66 lines

What it actually says

<research_flow>

<description_and_purpose> Orchestrates deep research via meta-prompting: craft an optimized research prompt, then execute it in a dedicated subagent. </description_and_purpose>

<workflow_phases>

<prerequisites phase="0", applies="ALL">

  1. All Rosetta prep steps MUST be FULLY completed
  2. USE SKILL load-project-context, orchestration, hitl
  3. MUST ALWAYS use todo tasks ledger, ASAP. Phases are sequential. Independent tasks can run in parallel.
  4. Orchestrator trusts the system and skills; coordinates sequence, artifacts, state, and approvals only.
  5. Workflow state MUST be saved to agents/TEMP/<FEATURE>/research-flow-state.md file.
  6. If /goal is set repeat phases 3-4 until goal is met.

<context_load phase="1" subagent="researcher" role="Context gatherer for research scope" subagent_required_model="Claude Sonnet 5.5, GPT-6 Luna, Gemini 3.8 Flash">

  1. Read all lines from CONTEXT.md, ARCHITECTURE.md, and IMPLEMENTATION.md.
  2. Input: user research request. Output: loaded project context.
  3. Update research-flow-state.md.

</context_load>

<prompt_craft phase="2" subagent="researcher" role="Research prompt architect" subagent_required_model="Claude Opus 5.5, GPT-6 Luna, GPT-6.1 Sol, Gemini 4 Argon, Gemini 3.8 Flash">

  1. Create an optimized research prompt for the user request.
  2. Save as research-prompt.md in FEATURE PLAN folder. Output ONLY the optimized prompt.
  3. Input: user request + project context. Output: research-prompt.md.
  4. Required skills: reasoning
  5. Update research-flow-state.md.
  6. HITL approval of research prompt before execution.

</prompt_craft>

<execute_research phase="3" subagent="researcher" role="Deep research executor" subagent_required_model="Claude Sonnet 5.5, GPT-6 Luna, Gemini 3.8 Flash">

  1. Execute the approved research prompt as a separate subagent.
  2. Input: approved research-prompt.md. Output: docs/<feature>-research.md.
  3. Required skills: research
  4. Update research-flow-state.md.

</execute_research>

  1. Finalize docs/<feature>-research.md.
  2. Input: completed research document. Output: finalized research document.
  3. Update research-flow-state.md and mark complete.

</workflow_phases>

</research_flow>

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. 13d ago Changed 32c066fbb4f8
  2. 14d ago Changed b1beeaffb2f6
  3. 1mo ago First seen · 66 lines · 17 tokens per session scan A 20837ca5ec2e

Subscribe to this mod's changes

research-flow is a command published in the GitHub repository griddynamics/rosetta (363 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 655 once invoked, about $0.0001 per session on Opus 5.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-09-03.

Claude CodeResearchcodexcopilotcursordeveloper-toolsmcp-serverworkflow
Related

Other commands, from other repositories

OPSX: Propose

Propose a new change - create it and generate all artifacts in one step.

ZhaoYis/My-Skills · 21 tokens

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

speckit.bug.fix

Apply the remediation from a bug assessment and record what was changed.

github/spec-kit · 12 tokens