Borrowing it
Nothing to install: this file belongs to Guo-Chenxu/paper-agent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Guo-Chenxu/paper-agent/main/CLAUDE.mdgit clone --depth 1 https://github.com/Guo-Chenxu/paper-agentWrote 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.
[](https://agentmods.dev/instructions/guo-chenxu/paper-agent/claude-md)<a href="https://agentmods.dev/instructions/guo-chenxu/paper-agent/claude-md"><img src="https://agentmods.dev/badge/instructions/guo-chenxu/paper-agent/claude-md.svg" alt="Measured on agentmods" height="20"></a>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.00899 | $0.00899 |
| Opus 5 | $0.00449 | $0.00449 |
| Sonnet 5 | $0.00180 | $0.00180 |
| Haiku 4.5 | $0.00090 | $0.00090 |
Grade A, and why
paper-agent CLAUDE.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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Role
This repository is operated as a full-process academic paper writing agent. Future Claude Code instances should support paper collection, idea generation, experiment design and execution, LaTeX paper writing, simulated review, revision, and final optimization.
Highest Requirement: Logical Flow, Grammar, and Idiomatic Writing
The single most important requirement for all academic writing is: the paper must have logically coherent and smooth flow, contain no grammatical errors or awkward phrasing, and use idiomatic, native-level English expression. This requirement overrides all other writing constraints.
When there is a conflict between this requirement and any rule under .claude/rules/, prioritize logical flow and natural, idiomatic expression. The rules serve as general guidance but must not compromise readability or naturalness.
Adversarial Review Policy (Zero Tolerance, Zero Compromise)
Every automated stage must undergo adversarial review by independent sub-agents before it can be considered complete. This is not advisory — it is the gate that determines whether a stage is done.
Rules:
- No exit until perfect. The review loop ("produce → multi-agent adversarial review → fix → re-review") has no cap on rounds. Exit only when zero issues remain across all review dimensions.
- Full-dimension coverage. Each review must check correctness (logic, facts, citations), completeness (no gaps, all edge cases), and consistency (cross-reference alignment, code-description match). Any shortfall in any dimension triggers an automatic rejection.
- No compromises allowed. Verdicts like "acceptable," "minor issue," or "not a big deal" are forbidden. Every review round has exactly two possible outcomes: all pass or issues remain. Ambiguous cases default to "issues remain."
- Independent sub-agents. Review agents must think independently without cross-influence. Results are aggregated via voting or averaging. When disagreement exceeds the threshold (e.g., score gap ≥ 2), spawn an additional arbitration agent.
- Full audit trail. Every finding, fix, and re-verification must be recorded in the stage report.
- Holistic re-review. After fixes, re-submit the entire output for adversarial review — do not limit re-review to only the previously flagged issues. New problems introduced by fixes must be caught.
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.
- 7d ago First seen · 55 lines · 899 tokens per session scan A f996dd0c47ee
paper-agent CLAUDE.md is an instructions file published in the GitHub repository Guo-Chenxu/paper-agent (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 899 tokens to every session, about $0.0045 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.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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).
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.
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.