research-scan AGENTS.md

research-scan AGENTS.md is an instructions file for Codex, OpenCode from Synectic-Research/research-scan. It costs 10,844 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for research-scan, a tool that discovers and evaluates research papers within a publication window. They define terms such as a run, candidate ID, discovery origin, and stages performed by the agent or command-line tool.

In plain words
What is it for?
Use them when working on research-scan behavior, its specification, commands, entry surface, or evaluation process.
Why use it?
They give contributors a shared vocabulary and rules for changing the repository safely. They also explain how papers and scan files are identified and organized.

Instructions file for CodexOpenCode

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.

agentmods
npx agentmods add instructions/synectic-research/research-scan/agents-md
Clone the repo
git clone --depth 1 https://github.com/Synectic-Research/research-scan

Made for: Codex, OpenCode.

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 research-scan AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/synectic-research/research-scan/agents-md.svg)](https://agentmods.dev/instructions/synectic-research/research-scan/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/synectic-research/research-scan/agents-md"><img src="https://agentmods.dev/badge/instructions/synectic-research/research-scan/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 10,844 This file is loaded in full into every session.
When invoked 10,844 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.10844 $0.10844
Opus 5 $0.05422 $0.05422
Sonnet 5 $0.02169 $0.02169
Haiku 4.5 $0.01084 $0.01084

Measured 4d ago against content hash 98146f905d18, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

research-scan AGENTS.md 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 4d 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.

AGENTS.md · 559 lines

How it starts

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

AGENTS.md — research-scan

Operating doctrine for this repo. Spec of record: research-scan-v1-spec.md — read the relevant section before changing behaviour it defines. Section references below (§9, §10.4) are to it.

Vocabulary

  • run — one scan. A directory research/scans/<YYYY-MM-DD>-<slug>/ holding every stage's file, relative to the process's cwd: the repo for a local scan, $RESEARCH_SCAN_MCP_DATA/<scan_id>/ for one driven through the MCP adapter.
  • cid — stable candidate id: first 12 hex of sha1 of the primary identifier, in the priority order doi > arxiv > pmid > norm(title)+year (§8.2). The join key across every file.
  • origin — one discovery path that found a candidate (query, references, citations, recommendations). A paper keeps every origin it earns; origin count is a ranking signal.
  • in-window / outside-window — inside the publication window, or an expansion reference from before it. Out-of-window papers are tagged, never dropped, and fill the foundational slots.
  • [A] stage / [C] stage — a stage the agent performs under a rubric, versus one the CLI performs deterministically. plan, screen, rerank are [A]; everything else is [C].
  • verified / flagged — a packet whose DOI resolved and whose title, year and first author match the live record, versus one kept with mismatches[] and an [UNVERIFIED] marker. Never silent.
  • purposebuild | research | orient, declared on the brief's Purpose: line or inferred by the planner and written into the first sentence of brief_summary. Decides what counts as impact: which sub_criteria set is derived, what why_it_matters must argue, what screening rewards, and how the judge reads relevance. Not a schema field — it lives in prose, on purpose.
  • profilequick | standard | deep, chosen at init and recorded in manifest.defaults. Sets per-query depth, the pool cap, the out-of-window total for the run, and whether the gap round runs. Flags still override it.
  • gap round — V1.1's one extra retrieval round, aimed by coverage.json at the sub-criteria round 1 covered thinnest. queries.json.round2 holds its queries, rNN/xrNN its batches. It runs exactly once; "round 1 / round 2" already means the screening passes, hence the name.
  • slice — S0…S6 in §15. One slice = one commit = one demoable gate.

Read the full file on GitHub · 559 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. 4d ago First seen · 559 lines · 10,844 tokens per session scan A 98146f905d18

Subscribe to this mod's changes

research-scan AGENTS.md is an instructions file published in the GitHub repository Synectic-Research/research-scan (0 stars, last pushed 7d ago), licensed Apache-2.0. It adds 10,844 tokens to every session, about $0.0542 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-31.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens