What is 0-osp-onboarding?

An onboarding stage in Open ScholarPeer, a workflow for reviewing research papers. It identifies the review venue, finds the paper, converts it to readable text when needed, and prepares review criteria.

It is for locating papers, creating .brain/input/paper.md, and scaffolding venue-specific review guidelines and questions.

It removes the setup work needed before analyzing a paper and gives later stages a consistent input file.

0-osp-onboarding — Command for Claude Code by amirkiarafiei

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/amirkiarafiei/open-scholar-peer/0-osp-onboarding/github.svg)](https://agentmods.dev/commands/amirkiarafiei/open-scholar-peer/0-osp-onboarding)

Your own site

<a href="https://agentmods.dev/commands/amirkiarafiei/open-scholar-peer/0-osp-onboarding"><img src="https://agentmods.dev/badge/commands/amirkiarafiei/open-scholar-peer/0-osp-onboarding/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/amirkiarafiei/open-scholar-peer/0-osp-onboarding"><img src="https://agentmods.dev/badge/commands/amirkiarafiei/open-scholar-peer/0-osp-onboarding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,390 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.

Model	Per session	Once invoked
Fable 5.1	$0.00014	$0.01390
Opus 5	$0.00007	$0.00695
Sonnet 5	$0.00003	$0.00278
Haiku 4.5	$0.00001	$0.00139

Measured 12d ago against content hash 308b2c166d85, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

0-osp-onboarding 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 12d 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/.claude/commands/0-osp-onboarding.md · 100 lines

How it starts

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

/0-osp-onboarding — Stage 0: Onboarding

Prepares the review environment. Must run before any other numbered step.

Activation

Invoke the osp-orchestrator skill (no domain persona needed for this step).

Steps

1. Read session state

Read .brain/session.json. If missing, run scripts/init_brain.sh first or initialize a default per the v2 schema.
If phases.onboarding.status == "completed" and qa_criteria is non-empty, ask the user whether to re-run (which would overwrite 00_review_guidelines.md and any pre-scaffolded 05_qa_*.md files). If they decline, exit.

2. Locate the paper and ensure a readable text version

Check .brain/input/ for a paper file. Common extensions: .pdf, .md, .tex, .docx.
If empty, ask the user where the paper is. Help them collaboratively — accept any path, then copy the file into .brain/input/.
Always produce .brain/input/paper.md (the canonical readable form):
- If the original is .md, ensure it's named paper.md (rename if necessary).
- If the original is .pdf / .docx / .tex, attempt conversion with the markitdown MCP tool (markitdown.convert). Save output to .brain/input/paper.md.
- If markitdown is unavailable, do not silently advance. Tell the user explicitly that downstream phases require paper.md and offer two options: (a) install markitdown (uvx markitdown-mcp), or (b) provide a manual markdown conversion. Pause until one is in place.
Save paper.path (original) and paper.parsed_path (the canonical .brain/input/paper.md) into session.json.

3. Identify the venue

Always ask the user explicitly, even if the paper's title page, header, or metadata already shows a venue. Do not auto-fill from the paper.
Use your tool's native ask/input mechanism if one is available (e.g. ask_user, an interactive prompt, or a confirmation dialog). If no native ask exists, print the question and wait for a reply before continuing.
Ask: "Which venue or journal are you reviewing for? (e.g. ICLR 2026, NeurIPS 2025, Nature Machine Intelligence, arXiv-only)"
If the paper appears to list a venue, show what you found and ask the user to confirm or correct it: "The paper mentions [venue]. Is that the submission venue you want to review against, or a different one?"
Save venue.name and venue.year to session.json.

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

12d ago First seen · 100 lines · 14 tokens per session scan A 308b2c166d85

Subscribe to this mod's changes

0-osp-onboarding is a command published in the GitHub repository amirkiarafiei/open-scholar-peer (28 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 1,390 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-30.

Research academic-paper-review ai-agents ai-peer-review peer-review research-paper research-tool

0-osp-onboarding

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/0-osp-onboarding — Stage 0: Onboarding

Activation

Steps

1. Read session state

2. Locate the paper and ensure a readable text version

3. Identify the venue

What this file has done since we first saw it

Other commands, from other repositories

ars-mark-read

ars-cache-invalidate

ars-unmark-read

ars-disclosure

ars-revision-coach

ars-rebuttal-audit