What is paper-verify AGENTS.md?

Project instructions for paper-verify, a local Python tool that checks whether citations are supported by their sources. It extracts citations, fetches sources, judges the matches, scores them, and creates a report.

Use it when developing or maintaining paper-verify. Work through one feature at a time, run its verification command, and use feature_gate.py to detect false or outdated completion states.

It provides a controlled way to verify progress instead of relying on a manually edited record. A feature is marked complete only after its verification command succeeds.

How nolainjin/paper-verify configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to nolainjin/paper-verify. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/nolainjin/paper-verify/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/nolainjin/paper-verify

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/nolainjin/paper-verify/agents-md/github.svg)](https://agentmods.dev/instructions/nolainjin/paper-verify/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/nolainjin/paper-verify/agents-md"><img src="https://agentmods.dev/badge/instructions/nolainjin/paper-verify/agents-md/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/instructions/nolainjin/paper-verify/agents-md"><img src="https://agentmods.dev/badge/instructions/nolainjin/paper-verify/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 588 This file is loaded in full into every session.

When invoked 588 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.

Model	Per session	Once invoked
Fable 5.1	$0.00588	$0.00588
Opus 5.5	$0.00235	$0.00235
Sonnet 5.5	$0.00118	$0.00118
Haiku 4.5	$0.00059	$0.00059

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

Security

Grade A, and why

paper-verify 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 2mo 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 · 47 lines

How it starts

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

AGENTS.md — paper-verify

Short entrypoint for coding agents. Detail lives in linked files (progressive disclosure).

What this is

A citation-verification tool (extract → fetch → judge → score → report). Pure-Python, local-first. See README.md for the product; pyproject.toml for deps.

Feature list is the source of truth (harness primitive)

feature_list.json is the single record of what must work and whether it does — not a human note. Each feature = (behavior, verification command, state, evidence).

Rules (do not bypass):

One feature active at a time. Pick the next not-started whose dependencies are passing.

A feature reaches passing ONLY via its verification command exiting 0. Never hand-edit state to passing. The gate controls the transition:

source .venv/bin/activate
python tools/feature_gate.py            # report drift / LIEs (state=passing must verify)
python tools/feature_gate.py --sync     # promote verified features to passing (+evidence)

state: passing with a failing verification is a GATE FAIL (exit 1) — the false-"done" guard. Wire feature_gate.py into pre-commit / CI to make it un-bypassable.
Back-pressure = count of non-passing features. 0 = done.

Verify before claiming done

Full suite: python -m pytest -q (must stay green).
The feature gate is the per-feature gate; the suite is the global gate.

Dev setup

Recreate the venv if missing: python -m venv .venv && .venv/bin/pip install -e '.[dev]'
Full suite: .venv/bin/python -m pytest -q

Provider neutrality (hard constraints)

Do not rewrite the verifier core for one provider; no permanent provider branches — provider differences live in paperverify/harness/ and docs/providers/.
Keep tests network-free (monkeypatch fetch/judges) unless clearly marked as integration.
Generated *_report.md / *_claims.jsonl stay out of commits (.gitignore covers them).

Conventions

SSoT: schema version in paperverify/report.py (SCHEMA_VERSION); IPC/shape changes bump it.
Backlog/audit: docs/harness/2026-06-04_paper-verify-audit/ (note: a static doc — it drifts; feature_list.json + the gate are authoritative for current state).

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

2mo ago First seen · 47 lines · 588 tokens per session scan A 66c6f35756a0

Subscribe to this mod's changes

paper-verify AGENTS.md is an instructions file published in the GitHub repository nolainjin/paper-verify (7 stars, last pushed 1mo ago), licensed MIT. It adds 588 tokens to every session, about $0.0024 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-31.

Citation LLM Research arxiv doi fact-checking mcp

paper-verify AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
paper-verify AGENTS.mdnolainjin/paper-verify	Instructions file	7	1mo ago	MIT	A	588	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

paper-verify: Instructions file for Codex