research-scientist

research-scientist is an agent for Claude Code from cdeust/ai-architect-mcp-codebase. It costs 23 tokens per session (3,123 once invoked), scanned A, original, MIT.

An agent role for researching neuroscience papers, information-retrieval research, and technical causes of benchmark failures.

In plain words
What is it for?
Use it to review papers, analyse benchmark history, study failure modes, compare approaches, and save findings in the project's research memory.
Why use it?
It gives research work a repeatable process for checking prior findings, identifying gaps, and recording results.

Agent for Claude Code

Part of the ai-architect-mcp-codebase plugin — 3 skills, 24 commands, 18 agents, 6 hooks, 2 MCP servers shipped together

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/cdeust/ai-architect-mcp-codebase/research-scientist
Clone the repo
git clone --depth 1 https://github.com/cdeust/ai-architect-mcp-codebase

Made for: Claude Code.

Or install ai-architect-mcp-codebase, the plugin that ships this one along with the rest of its 3 skills, 24 commands, 18 agents, 6 hooks, 2 MCP servers.

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-scientist

README.md
[![agentmods](https://agentmods.dev/badge/agents/cdeust/ai-architect-mcp-codebase/research-scientist.svg)](https://agentmods.dev/agents/cdeust/ai-architect-mcp-codebase/research-scientist)
Your own site
<a href="https://agentmods.dev/agents/cdeust/ai-architect-mcp-codebase/research-scientist"><img src="https://agentmods.dev/badge/agents/cdeust/ai-architect-mcp-codebase/research-scientist.svg" alt="Measured on agentmods" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,123 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.00023 $0.03123
Opus 5 $0.00012 $0.01562
Sonnet 5 $0.00005 $0.00625
Haiku 4.5 $0.00002 $0.00312

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

Security

Grade A, and why

research-scientist 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.

.claude/agents/research-scientist.md · 231 lines

How it starts

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

You operate inside a project with a full MCP-based memory and RAG system. Use it as your research knowledge base.

Before Researching

  • recall prior research — papers already reviewed, mechanisms already implemented, experiments already run.
  • recall benchmark history — past scores, identified failure modes, what improvements were tried and their results.
  • recall_hierarchical for broad context on a research domain (e.g., "consolidation", "retrieval", "encoding").
  • get_causal_chain to understand how existing mechanisms connect — which modules feed into which.
  • detect_gaps to find under-explored areas in the knowledge graph.
  • assess_coverage to identify where knowledge coverage is weakest.

After Researching

  • remember paper reviews: citation, key insight, relevance to Cortex, applicability assessment, implementation feasibility.
  • remember benchmark analyses: which categories are weakest, root cause classification, proposed improvements.
  • remember negative results — what was tried and didn't work, and why. This prevents re-exploring dead ends.
  • remember competitive analysis: how other systems scored, what methods they disclosed.
  • anchor breakthrough insights or fundamental design decisions that should never be lost.

Research Continuity

The memory system IS the project you're improving. Your research findings feed directly into implementation. Use get_project_story to understand the arc of recent improvements before proposing the next one.

Read the full file on GitHub · 231 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.

  1. 4d ago First seen · 231 lines · 23 tokens per session scan A 5fc5f8407eea

Subscribe to this mod's changes

research-scientist is an agent published in the GitHub repository cdeust/ai-architect-mcp-codebase (4 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 3,123 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-31.

Related

Other agents, from other repositories

skill-author

Authors and edits brooks-lint skill content — the six shipped skills (skills/{name}/SKILL.md + {name}-guide.md) and the shared framework under skills/shared/. Knows the repo's hard conventions: the Iron Law finding form, the SKILL.md Setup→Process→Mode-line shape, guide step continuity, and the mandatory "Do NOT…

hyhmrright/brooks-lint · 98 tokens

consistency-qa

The brooks-lint verification gate. Runs npm run validate, npm test, and npm run evals, then cross-checks the documents the validator can't fully diff — the four plugin manifests, all six README badges, the docs landing-page JSON-LD, CHANGELOG, AGENTS.md, GEMINI.md, and the derived book count — for drift. Reports…

hyhmrright/brooks-lint · 123 tokens

eval-curator

Authors and maintains the brooks-lint eval suite in evals/evals.json — the benchmark scenarios covering R1–R6 (code decay) and T1–T6 (test decay), including the false-positive / tradeoff cases that must NOT be flagged. Ensures every new risk code or skill gets paired coverage and that the suite passes npm run evals.…

hyhmrright/brooks-lint · 97 tokens

release-manager

Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…

hyhmrright/brooks-lint · 85 tokens

trigger-boundary-auditor

Audits the trigger boundaries of the six brooks-lint skills for false-triggering risk and routing collisions. Use before a release, or after editing any SKILL.md description: field. Read-only — reports findings, makes no edits.

hyhmrright/brooks-lint · 56 tokens

code-explorer

Delegate to this agent for deep codebase exploration — semantic search, exact symbol lookup and reference tracing over a Beacon index. Use when the question requires understanding how multiple files connect.

sagarmk/beacon-plugin · 39 tokens