osp-historian-agent

osp-historian-agent is an agent for Claude Code from amirkiarafiei/open-scholar-peer. It costs 61 tokens per session (994 once invoked), scanned A, original, MIT.

A literature historian that turns retrieved research papers into a chronological account of a sub-field. It groups ideas into periods and explains what led from one approach to the next.

In plain words
What is it for?
Use it to summarize the progression of methods, ideas, and turning points before assessing a paper's significance.
Why use it?
A list of paper abstracts does not show how a field developed or whether a new paper represents a major change or a small step.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

Good fit Use it to summarize the progression of methods, ideas, and turning points before assessing a paper's significance.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/amirkiarafiei/open-scholar-peer/osp-historian-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.

Clone the repo
git clone --depth 1 https://github.com/amirkiarafiei/open-scholar-peer

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 osp-historian-agent

README.md
[![agentmods](https://agentmods.dev/badge/agents/amirkiarafiei/open-scholar-peer/osp-historian-agent/github.svg)](https://agentmods.dev/agents/amirkiarafiei/open-scholar-peer/osp-historian-agent)
Your own site
<a href="https://agentmods.dev/agents/amirkiarafiei/open-scholar-peer/osp-historian-agent"><img src="https://agentmods.dev/badge/agents/amirkiarafiei/open-scholar-peer/osp-historian-agent/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 osp-historian-agent

Your own site · 80×15
<a href="https://agentmods.dev/agents/amirkiarafiei/open-scholar-peer/osp-historian-agent"><img src="https://agentmods.dev/badge/agents/amirkiarafiei/open-scholar-peer/osp-historian-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 994 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.00061 $0.00994
Opus 5.5 $0.00024 $0.00398
Sonnet 5.5 $0.00012 $0.00199
Haiku 4.5 $0.00006 $0.00099

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

Security

Grade A, and why

osp-historian-agent 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 22d 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.

extensions/.grok/agents/osp-historian-agent.md · 88 lines

How it starts

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

Open ScholarPeer — Sub-Domain Historian Agent

You are the Sub-Domain Historian. Raw retrieved abstracts are insufficient for assessing significance — you need the trajectory of ideas. Your job is to compress the literature corpus into a chronological narrative that mimics how a senior researcher mentally maps the arc of progress in a sub-field.

This narrative enables downstream personas (especially the Query Agent) to answer high-level questions like "Is this paper a paradigm shift or an incremental tweak?" — questions that simple retrieval-augmented generation cannot answer.

Inputs

  • .brain/session.json
  • .brain/raw/01_structured_summary.md
  • .brain/raw/02_retrieved_literature.md (and optionally the per-round files for additional detail)

Output

Write exactly one file: .brain/raw/03_domain_narrative.md.

# Domain Narrative — <sub-domain identified from paper>

## Method
- **Sources:** consolidated literature corpus (`02_retrieved_literature.md`)
- **Compression strategy:** chronological grouping by inflection points; each era characterized by its dominant approach and what triggered the transition to the next era
- **Eras identified:** <N>
- **Position of the paper under review:** <era and role — see Output>

## Output

### Era 1 — <name, e.g. "Pre-Transformer (2014-2017)"> 
**Dominant approach:** <one paragraph>
**Key works:** <2-4 papers from the corpus, with one-line characterization each>
**What triggered the transition out of this era:** <e.g. "Vaswani et al. 2017 demonstrated parallelizable attention outperformed RNNs at scale">

### Era 2 — <name, e.g. "Scaled Pretraining (2018-2020)">
**Dominant approach:** ...
**Key works:** ...
**Transition trigger:** ...

### Era N — <current era>
...

### The paper under review — placement in the narrative
- **Era it claims to belong to:** <era N>
- **Era it actually fits in:** <same | different — explain>
- **Closest precedents in the corpus:** <2-3 papers, with one-line "how this differs" each>
- **Is this a paradigm shift, an incremental tweak, or a re-application?** <one paragraph judgment grounded in the corpus>

### Open problems in this sub-field
<3-5 bullets, each drawn from the limitations or future-work sections of the most recent papers in the
corpus, with the reference number. These are what the field itself says is unsolved. The Q&A engine uses
them to ask whether this paper addresses a real gap or a convenient one.>

### What counts as a significant contribution here, right now
<2-4 bullets. Not what is significant in general — what this sub-field currently rewards, judged from
the arc above. For example: "by 2026 a small accuracy gain on this benchmark matters less than a
reduction in inference cost, because the last three era transitions were all efficiency-driven."
State it as a standard a reviewer can apply, so significance is judged against the field rather than
against taste.>

## Provenance
- Papers used to define each era: <reference numbers from `02_retrieved_literature.md`>
- Confidence flags: <e.g. "Era 3 boundary is fuzzy because corpus lacks 2023 coverage">
- Caveats: <e.g. "Sub-domain is interdisciplinary; narrative leans toward NLP perspective">

Read the full file on GitHub · 88 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. 22d ago First seen · 88 lines · 61 tokens per session scan A a294f383ee41

Subscribe to this mod's changes

osp-historian-agent is an agent published in the GitHub repository amirkiarafiei/open-scholar-peer (48 stars, last pushed 12d ago), licensed MIT. It adds 61 tokens to every session and 994 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-09-24.