osp-historian-agent

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

A workflow that turns a collection of research papers into a chronological explanation of how a field developed. It groups major changes in approach and describes what led researchers from one period to the next.

In plain words
What is it for?
Use it to explain the history of a research area, place a paper in that timeline, and judge whether its contribution changes the field or extends existing work.
Why use it?
A list of paper summaries does not show how ideas and methods evolved over time.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to explain the history of a research area, place a paper in that timeline, and judge whether its contribution changes the field or extends existing work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/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.

Any agent
npx skills add amirkiarafiei/open-scholar-peer --skill osp-historian-agent
Clone the repo
git clone --depth 1 https://github.com/amirkiarafiei/open-scholar-peer

Made for: Claude Code, Codex.

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/skills/amirkiarafiei/open-scholar-peer/osp-historian-agent/github.svg)](https://agentmods.dev/skills/amirkiarafiei/open-scholar-peer/osp-historian-agent)
Your own site
<a href="https://agentmods.dev/skills/amirkiarafiei/open-scholar-peer/osp-historian-agent"><img src="https://agentmods.dev/badge/skills/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/skills/amirkiarafiei/open-scholar-peer/osp-historian-agent"><img src="https://agentmods.dev/badge/skills/amirkiarafiei/open-scholar-peer/osp-historian-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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 1mo 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 1mo 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/.agent/skills/osp-historian-agent/SKILL.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. 1mo ago Changed · +12 lines a294f383ee41
  2. 2mo ago First seen · 76 lines · 61 tokens per session scan A aee10159782a

Subscribe to this mod's changes

osp-historian-agent is a skill published in the GitHub repository amirkiarafiei/open-scholar-peer (51 stars, last pushed 6d 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-08-30.

Related

Other skills, from other repositories

ara-rigor-reviewer

Performs ARA Seal Level 2 semantic epistemic review on Agent-Native Research Artifacts, scoring six dimensions (evidence relevance, falsifiability, scope calibration, argument coherence, exploration integrity, methodological rigor) and producing a constructive, severity-ranked report with a Strong Accept-to-Reject…

Orchestra-Research/AI-Research-SKILLs · 91 tokens

baseline-comparison-audit

Audit whether a paper's baseline comparisons are COMPLETE, FAIR, and SIGNIFICANT: a required recent SOTA baseline is missing while 'best/SOTA' is claimed (HP-MISSING-BASELINE); a baseline is undertuned / given less compute-tuning-data, run at a mismatched config, or the equal-budget ablation-as-baseline is absent…

wanshuiyin/Anti-Autoresearch · 310 tokens

eval-design-forensics

Audit whether a paper's EVALUATION DESIGN actually measures what it claims and whether its reporting is complete — the validity layer family D (experiment-forensics) cannot reach. Three patterns: train/test leakage means the reported score may not measure generalization (HP-EVAL-LEAKAGE — adopts the Kapoor & Narayanan…

wanshuiyin/Anti-Autoresearch · 458 tokens

novelty-duplication-advisory

MEMO-ONLY prior-work overlap advisory: surfaces the two ADVISORY taxonomy signals neither a tool nor a model can decide from the paper alone — ADV-TRIVIAL-COMBINATION (standard A+B+C / 缝合 stapling) and ADV-DUPLICATE-PUBLICATION (repackaged / duplicate submission). The executor RETRIEVES candidate prior work (DBLP…

wanshuiyin/Anti-Autoresearch · 284 tokens

anti-autoresearch

End-to-end substantive-integrity forensic sweep of a research paper (especially autoresearch / AI-Scientist-style output). Orchestrates the whole pipeline: ingest (arxiv-id | pdf | dir → working dir + pdftotext for L0) → /evidence-ledger (artifact manifest + observability level L0/L1/L2 + span-anchored claims.json) →…

wanshuiyin/Anti-Autoresearch · 275 tokens

adversarial-case-builder

Synthesize the single strongest EVIDENCE-BOUND reviewer case to reject a paper, built ONLY from the evidence ledger (claims.json) + the other auditors' confirmed findings — never free-floating LLM critique. Two fresh cross-model codex threads: an attack writes the 200-word rejection paragraph (every accusation tagged…

wanshuiyin/Anti-Autoresearch · 194 tokens