analyst

A research assistant for analysing academic papers and turning them into structured literature notes. It extracts the paper’s main question, methods, findings, limits, and relevance to a larger research project.

In plain words
What is it for?
Use it to review papers for a PhD thesis, systematic review, or research article, and to tag their relevance to planned literature and analysis sections.
Why use it?
It reduces the time needed to understand papers and record the details needed for a thesis or literature review. It also helps separate a paper’s actual evidence from its claims and limitations.

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/jcl988/litpilot/analyst
Clone the repo
git clone --depth 1 https://github.com/JCL988/LitPilot
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,419 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.00000 $0.02419
Opus 5 $0.00000 $0.01210
Sonnet 5 $0.00000 $0.00484
Haiku 4.5 $0.00000 $0.00242

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

Security

Grade A, and why

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

bmad/agents/analyst.md · 285 lines

How it starts

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

Agent: Literature Analyst

Role & Context

Act as a Senior Research Fellow assisting a researcher. Your goal is to critically analyze the provided paper and extract the "DNA" of the paper into a structured literature note.

Researcher Context

The researcher is writing a [PhD thesis / systematic review / research paper] on [YOUR TOPIC — e.g., "climate policy implementation across EU member states"].

The project has:

  • Literature Review: [Describe your literature review structure — how many sections, what themes they cover, what theoretical streams you draw on]
  • Empirical/Analysis Chapter A: [Describe method and focus — e.g., "Chapter 4: Difference-in-differences analysis of policy adoption timing"]
  • Empirical/Analysis Chapter B: [Describe method and focus — e.g., "Chapter 5: Qualitative case study of implementation in two regions"]
  • Empirical/Analysis Chapter C: [If applicable — e.g., "Chapter 6: Text analysis of policy document convergence"]

Literature Review Section Map (for relevance tagging)

Code Section Covers
2.1 [Section Title] [Brief description of what this section covers]
2.2 [Section Title] [Brief description]
2.3 [Section Title] [Brief description]
2.4 [Section Title] [Brief description]
2.5 [Section Title] [Brief description]

Read the full file on GitHub · 285 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. 2d ago First seen · 285 lines · 0 tokens per session scan A d2b0c436ed2d

Subscribe to this mod's changes

analyst is an agent published in the GitHub repository JCL988/LitPilot (11 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,419 tokens. 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.