Borrowing it
Nothing to install: this file belongs to reviewtaipei284/awesome-claudecode-paper-proofreading. 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/reviewtaipei284/awesome-claudecode-paper-proofreading/main/AGENTS.mdgit clone --depth 1 https://github.com/reviewtaipei284/awesome-claudecode-paper-proofreadingWrote 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/reviewtaipei284/awesome-claudecode-paper-proofreading/agents-md)<a href="https://agentmods.dev/instructions/reviewtaipei284/awesome-claudecode-paper-proofreading/agents-md"><img src="https://agentmods.dev/badge/instructions/reviewtaipei284/awesome-claudecode-paper-proofreading/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.
<a href="https://agentmods.dev/instructions/reviewtaipei284/awesome-claudecode-paper-proofreading/agents-md"><img src="https://agentmods.dev/badge/instructions/reviewtaipei284/awesome-claudecode-paper-proofreading/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.01274 | $0.01274 |
| Opus 5 | $0.00637 | $0.00637 |
| Sonnet 5 | $0.00255 | $0.00255 |
| Haiku 4.5 | $0.00127 | $0.00127 |
Grade A, and why
awesome-claudecode-paper-proofreading 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 12d 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.
This is a copy
100% identical to awesome-claudecode-paper-proofreading AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Paper Proofreading Agent
Purpose
Use this repository as a two-phase proofreading system for robotics and computer-vision papers written in LaTeX.
The detailed, authoritative review instructions live in:
prompts/01_latex_workspace_review.mdprompts/02_paper_proofreading.md
This AGENTS.md is a coordinator for Codex, not a replacement for those files.
The operating principle is always the same:
- Detect issues first.
- Do not edit anything during detection.
- Wait for the user to choose what to fix.
- Apply only the approved fixes.
Preserve the paper's technical meaning, claims, and author voice. Improve correctness and clarity without introducing new scientific content.
When To Use Which Workflow
Choose the workflow based on the user's request.
Workflow 1: LaTeX Workspace Review
Use this when the user asks for a workspace audit, LaTeX review, submission sanity check, preamble check, reference check, bibliography check, or similar infrastructure-focused proofreading.
Primary checklist:
prompts/01_latex_workspace_review.md
Focus areas:
- preamble and package configuration
- macro safety and naming consistency
- references, labels, bibliography, figures, and hidden submission mistakes
Workflow 2: Paper Proofreading
Use this when the user asks for paper proofreading, language review, conference-style reviewer feedback, clarity review, or final manuscript polishing.
Primary checklist:
prompts/02_paper_proofreading.md
Focus areas:
- language and grammar
- scientific clarity and overclaiming
- structure, captions, notation, and final-manuscript polish
If Both Apply
Run the workspace review first, then the paper proofreading pass.
Source Of Truth
Treat the prompt files as the source of truth for review criteria and edge cases.
- Use this
AGENTS.mdto decide which workflow to run and to preserve the two-phase behavior. - Use the prompt files for the actual checklist content.
- If the prompt files are missing, say that the full review instructions are unavailable rather than pretending this file is sufficient on its own.
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.
- 12d ago First seen · 178 lines · 1,274 tokens per session scan A 29ead0d3f6be
awesome-claudecode-paper-proofreading AGENTS.md is an instructions file published in the GitHub repository reviewtaipei284/awesome-claudecode-paper-proofreading (2 stars, last pushed 2d ago), licensed MIT. It adds 1,274 tokens to every session, about $0.0064 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to awesome-claudecode-paper-proofreading AGENTS.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
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.
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).
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.
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).