osp-rules

osp-rules is a cursor rule for Cursor from amirkiarafiei/open-scholar-peer. It costs 1,701 tokens per session, scanned A, original, MIT.

A set of always-on rules for Open ScholarPeer, a workflow for reviewing research papers. It controls how review steps read files, track progress, and use different roles.

In plain words
What is it for?
It helps manage paper-review state, route commands to the correct step, and record completed phases in .brain/session.json.
Why use it?
It prevents review steps from losing their place, loading unrelated files, or mixing responsibilities. It also makes reruns and unfinished work visible.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/. Also seen: mentions subagents.

Good fit It helps manage paper-review state, route commands to the correct step, and record completed phases in .brain/session.json.

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

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-rules

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

Your own site · 80×15
<a href="https://agentmods.dev/rules/amirkiarafiei/open-scholar-peer/osp-rules"><img src="https://agentmods.dev/badge/rules/amirkiarafiei/open-scholar-peer/osp-rules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,701 This file is loaded in full into every session.
When invoked 1,701 The same file — it is already loaded in full.
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.01701 $0.01701
Opus 5.5 $0.00680 $0.00680
Sonnet 5.5 $0.00340 $0.00340
Haiku 4.5 $0.00170 $0.00170

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

Security

Grade A, and why

osp-rules 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/.cursor/rules/osp-rules.mdc · 112 lines

How it starts

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

Open ScholarPeer — Always-On Rules

These rules apply automatically in any project where Open ScholarPeer is installed.

Brain protocol (apply on every invocation)

  1. Read .brain/session.json first to understand current state.
  2. Load only the artifacts in the active step's reads: contract. Do not load the full .brain/ directory. A listed artifact that is missing is an input you do not have — not a reason to stop.
  3. Update session.json around every step. Set started_at when you begin. On finishing, set the matching phases.<name> block to completed, set completed_at, and update resume_from.
  4. When the user moves past a step without running it, record that. Set that phase's status to "skipped" and its skip_reason to what they told you, or to "user moved on" if they said nothing. Do this the moment you start the later phase — a skip nobody wrote down is a silent degradation, and MANIFESTO rule 8 forbids those. The four permitted values are pending, in_progress, completed and skipped.
  5. Carry every skip forward. Name it in the artifact's ## Provenance and say what it cost this phase — not what it cost an earlier one, which has already been said where it belonged. Each phase reports its own consequence, once. /6-osp-review collects them all under ## What this review did not have, so whoever reads the review can tell a thin corpus from a thorough one. State it; do not repeat it, and never dress it as a warning.
  6. Re-runs overwrite with a warning. If a step is already completed, print one warning, then proceed.

Persona discipline

  • Each numbered command (/N-osp-*) activates exactly one persona skill (osp-<name>-agent). Do not blend personas.
  • The Q&A engine (/5-osp-qa) uses two personas at once: Query Agent (main thread) and Answer Generator (subagent, or self-reflection on tools that lack subagents).
  • The orchestrator (osp-orchestrator) never performs review work — it only routes.

Read the full file on GitHub · 112 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 · +49 lines · +833 tokens per session 17e44c5aa365
  2. 1mo ago Changed 53c8fbeaa3fc
  3. 2mo ago First seen · 63 lines · 868 tokens per session scan A fd4c71f15535

Subscribe to this mod's changes

osp-rules is a cursor rule published in the GitHub repository amirkiarafiei/open-scholar-peer (51 stars, last pushed 5d ago), licensed MIT. It adds 1,701 tokens to every session, about $0.0068 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.