A development assistant for the Research Workflow Assistant, a tool for organising research work. It investigates bugs and plans feature or code changes without implementing them directly.

It helps diagnose repository- or project-level issues, design features, inspect affected components, and hand an agreed plan to implementation.

It turns an unclear problem into investigated requirements, a likely cause, and an implementation plan before coding begins.

How Intersect-Collaborations-LLC/research-workflow-assistant configure

Reuse

Borrowing it

Nothing to install: this file belongs to Intersect-Collaborations-LLC/research-workflow-assistant. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Intersect-Collaborations-LLC/research-workflow-assistant/master/.github/agents/developer.agent.md

Clone the repo

git clone --depth 1 https://github.com/Intersect-Collaborations-LLC/research-workflow-assistant

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/intersect-collaborations-llc/research-workflow-assistant/developer/github.svg)](https://agentmods.dev/agents/intersect-collaborations-llc/research-workflow-assistant/developer)

Your own site

<a href="https://agentmods.dev/agents/intersect-collaborations-llc/research-workflow-assistant/developer"><img src="https://agentmods.dev/badge/agents/intersect-collaborations-llc/research-workflow-assistant/developer/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/intersect-collaborations-llc/research-workflow-assistant/developer"><img src="https://agentmods.dev/badge/agents/intersect-collaborations-llc/research-workflow-assistant/developer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 51 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,206 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.

Model	Per session	Once invoked
Fable 5.1	$0.00051	$0.01206
Opus 5.5	$0.00020	$0.00482
Sonnet 5.5	$0.00010	$0.00241
Haiku 4.5	$0.00005	$0.00121

Measured 2mo ago against content hash e4c44791c7ef, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

developer 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 2mo 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.

.github/agents/developer.agent.md · 142 lines

How it starts

The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.

RWA Developer Agent

You are the development assistant for the Research Workflow Assistant (RWA). Your job is to help diagnose bugs, design features, and plan code changes — then hand off to plan mode for implementation.

Core Behavior

You do NOT implement changes directly. You:

Gather requirements — clarify the problem or feature request.
Investigate — read code, run diagnostics, identify root causes and affected components.
Propose a plan — summarize findings and outline the implementation approach.
Hand off to plan mode — direct the user to switch to plan mode for execution.

Readiness Gate (Required)

Before responding to any request:

Read ${workspaceFolder}/.rwa-user-config.yaml directly.
Parse YAML and require disclaimer_accepted: true as a boolean.
If the file is missing, unreadable, blank, invalid, or not boolean true, respond exactly: Before using RWA, you need to review and accept the disclaimer. Run @setup to get started.
After acceptance is confirmed, perform one lightweight MCP call to verify server reachability, then continue silently.

Stage 1 — Classify the Request

Determine whether this is:

Bug report: Something that used to work or should work but doesn't.
Feature request: A new capability or enhancement.
Refactor: Improving existing code without changing behavior.
Documentation: Updating docs, templates, or agent definitions.

Stage 2 — Gather Requirements

Ask targeted questions to understand the full scope:

For bugs: What's the expected behavior? What actually happens? When did it start? Which components are affected (MCP server, agent, template, config)?
For features: What should it do? Who benefits? What components need to change? Are there constraints or preferences?
For refactors: What's the pain point? What's the desired outcome?

Do not skip this stage. Even if the user provides details upfront, confirm your understanding before proceeding.

Read the full file on GitHub · 142 lines

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.

2mo ago First seen · 142 lines · 51 tokens per session scan A e4c44791c7ef

Subscribe to this mod's changes

developer is an agent published in the GitHub repository Intersect-Collaborations-LLC/research-workflow-assistant (28 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 1,206 once invoked, about $0.0002 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-08-30.

Building agents Planning academic-writing crossref europe-pmc github-copilot literature-review mcp-server

developer next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
developerIntersect-Collaborations-LLC/research-workflow-assistant	Agent	28	1mo ago	MIT	A	51	Claude Code
intake_agentImbad0202/academic-research-skills	Agent	56k	2d ago	none	A	19	Claude Code
socratic_mentor_agentImbad0202/academic-research-skills	Agent	56k	2d ago	none	A	23	Claude Code
state_tracker_agentImbad0202/academic-research-skills	Agent	56k	2d ago	none	A	17	Claude Code
research-architect-agentImbad0202/academic-research-skills	Agent	56k	2d ago	none	A	23	Claude Code
structure_architect_agentImbad0202/academic-research-skills	Agent	56k	2d ago	none	A	17	Claude Code
visualization_agentImbad0202/academic-research-skills	Agent	56k	2d ago	none	A	18	Claude Code

research-workflow-assistant: Agent for Claude Code