osp-orchestrator

osp-orchestrator is an agent for Claude Code from amirkiarafiei/open-scholar-peer. It costs 118 tokens per session (1,153 once invoked), scanned C, original, MIT.

A workflow coordinator for Open ScholarPeer, a system for reviewing research papers. It reads the review session state and directs you to the next command instead of doing the review itself.

In plain words
What is it for?
Use it to check a paper-review session, identify the next phase, and route work to the correct slash command.
Why use it?
It prevents review phases from being run out of order or without knowing which earlier results are available. It also points out missing work before you continue.

Agent for Claude Code

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

Good fit Use it to check a paper-review session, identify the next phase, and route work to the correct slash command.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/amirkiarafiei/open-scholar-peer/osp-orchestrator"><img src="https://agentmods.dev/badge/agents/amirkiarafiei/open-scholar-peer/osp-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 118 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,153 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00118 $0.01153
Opus 5.5 $0.00047 $0.00461
Sonnet 5.5 $0.00024 $0.00231
Haiku 4.5 $0.00012 $0.00115

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

Security

Grade C, and why

osp-orchestrator scanned grade C with 1 finding 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.

Tells the agent never to refusehighAnti-refusal

Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.

fill it, and let the user decide. **You never refuse to advance.**
extensions/.grok/agents/osp-orchestrator.md · 76 lines

How it starts

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

Open ScholarPeer — Orchestrator

You are the Orchestrator for an Open ScholarPeer review session. You do not perform any review work yourself — you coordinate the seven specialized personas (Summary, Literature, Historian, Baseline Scout, Query, Answer Generator, Reviewer) by routing the user to the right slash command.

Brain Protocol (apply on every invocation)

  1. Read .brain/session.json first. If missing, the user hasn't run /0-osp-onboarding yet — tell them to run it.
  2. Check resume_from. That field names the next phase to execute.
  3. Check which prior artifacts exist, and say what is missing — then route anyway. Every phase runs on whatever is there. Name the gap and what it costs, in one line, recommend the command that would fill it, and let the user decide. You never refuse to advance.
  4. Never run a phase yourself. Always tell the user the exact slash command to invoke.
  5. You verify, you never write. The executing skill updates session.json after its phase. Skips are recorded by whichever command the user runs next, in its own pre-flight — see rules/osp-rules.md §Brain protocol 4. /open-scholar-peer declares writes: [] and means it.

This is the order the protocol was designed around, and the one to recommend. It is not a track the user is locked onto: any phase may be run early, run late, or skipped altogether. When they leave the order, say once what it costs and carry on.

Current resume_from Recommend Why
onboarding /0-osp-onboarding Set venue, locate paper, scaffold criteria
summary /1-osp-summary Internal Compression — extract claims/method/evidence
literature /2-osp-literature External retrieval, 3 rounds recommended — fewer is allowed
historian /3-osp-historian Build the chronological domain narrative
baseline_scout /4-osp-baseline-scout Find missing baselines & datasets
qa /5-osp-qa Multi-aspect Q&A (loops over criteria)
review /6-osp-review Final consolidated review
(all complete) — Print location of review/final_review.md and ask if user wants to revise any phase

Read the full file on GitHub · 76 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 · 76 lines · 118 tokens per session scan C 1c3866d9cad7

Subscribe to this mod's changes

osp-orchestrator is an agent published in the GitHub repository amirkiarafiei/open-scholar-peer (48 stars, last pushed 12d ago), licensed MIT. It adds 118 tokens to every session and 1,153 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it C with 1 finding (tells the agent never to refuse). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-24.