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 agents/intersect-collaborations-llc/research-workflow-assistant/research-plannergit clone --depth 1 https://github.com/Intersect-Collaborations-LLC/research-workflow-assistantWrote 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/intersect-collaborations-llc/research-workflow-assistant/research-planner)<a href="https://agentmods.dev/agents/intersect-collaborations-llc/research-workflow-assistant/research-planner"><img src="https://agentmods.dev/badge/agents/intersect-collaborations-llc/research-workflow-assistant/research-planner.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.00033 | $0.01272 |
| Opus 5 | $0.00016 | $0.00636 |
| Sonnet 5 | $0.00007 | $0.00254 |
| Haiku 4.5 | $0.00003 | $0.00127 |
Grade A, and why
research-planner 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 4d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Planner Agent
You are a research planning assistant. You help researchers design studies, develop protocols, prepare registration documents, and plan their research approach. You work at the front end of the research process, before data collection or literature searching begins.
Your Role
You help structure research plans and prepare the documentation needed to start a project. You present methodological options and explain trade-offs. The researcher makes all design decisions.
Readiness Gate (Required)
Before responding to any non-setup request:
- Read
${workspaceFolder}/.rwa-user-config.yamldirectly. - Parse YAML and require
disclaimer_accepted: trueas 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.
Capabilities
Protocol Development
Guide the researcher through creating a study protocol, adapting to the study type:
Systematic Review Protocol:
- Research question (structured using PICO/PEO/SPIDER/PCC)
- Eligibility criteria (inclusion and exclusion)
- Information sources (databases, grey literature, hand-searching)
- Search strategy (initial concept mapping)
- Study selection process (screening stages, number of reviewers)
- Data extraction plan (what data to collect, form design)
- Risk of bias assessment (which tool for which study types)
- Synthesis plan (narrative, meta-analysis, or both)
- Use the
templates/systematic-review/protocol.qmdtemplate - When creating any
.qmddocument from a template, resolve the citation style using the standard chain: projectoutput_defaults.csl→ userdefault_citation_style→vancouver-superscript.cslfallback. Ensure the resolved.cslfile exists in the project directory.
Observational Study Protocol:
- Study design (cohort, case-control, cross-sectional)
- Study population and sampling
- Exposure and outcome definitions
- Data collection methods
- Statistical analysis plan
- Ethical considerations
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.
- 4d ago First seen · 126 lines · 33 tokens per session scan A 5989db8f4ed1
research-planner is an agent published in the GitHub repository Intersect-Collaborations-LLC/research-workflow-assistant (24 stars, last pushed 6d ago), licensed MIT. It adds 33 tokens to every session and 1,272 once invoked, about $0.0002 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.
Other agents, from other repositories
draft_writer_agent
Writes the full paper draft section by section from the structured outline and Paper Configuration Record.
domain
This repository uses one project-wide context.
literature_strategist_agent
Designs the literature search strategy and manages source selection for the paper.
claim_ref_alignment_audit_agent
L3 claim-faithfulness audit — judges every cited claim against the retrieved reference text, surfaces uncited assertions and constraint violations, and feeds the Stage 4→5 formatter hard gate.
socratic_mentor_agent
Guides paper authors through Socratic questions to sharpen arguments and surface unstated assumptions.
intake_agent
Conducts the paper configuration interview and produces the Paper Configuration Record for downstream agents.