Borrowing it
Nothing to install: this file belongs to dengxu11111/dual-ai-paper-coach. 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/dengxu11111/dual-ai-paper-coach/main/CLAUDE.mdgit clone --depth 1 https://github.com/dengxu11111/dual-ai-paper-coachWrote 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/dengxu11111/dual-ai-paper-coach/claude-md)<a href="https://agentmods.dev/instructions/dengxu11111/dual-ai-paper-coach/claude-md"><img src="https://agentmods.dev/badge/instructions/dengxu11111/dual-ai-paper-coach/claude-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/dengxu11111/dual-ai-paper-coach/claude-md"><img src="https://agentmods.dev/badge/instructions/dengxu11111/dual-ai-paper-coach/claude-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.01975 | $0.01975 |
| Opus 5 | $0.00988 | $0.00988 |
| Sonnet 5 | $0.00395 | $0.00395 |
| Haiku 4.5 | $0.00198 | $0.00198 |
Grade A, and why
dual-ai-paper-coach 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 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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — your working rules in this project
This file is read automatically by Claude Code every time it enters this repo.
Project goal
Build a dual-AI paper writing + reviewing workflow. Claude Code (you) drafts the paper, revises it, and produces the submission package. Codex CLI (running in an isolated subprocess) reviews it. The two communicate only through files.
Writing yardstick: Science / Nature — broad-significance framing, Nature Reporting Summary statistical completeness, citation discipline, ≤ 5 display items. Most users will actually submit to GRL / ACP / JGR or similar; this repo deliberately measures drafts against the S/N ruler. The actual rules live in prompts/writer_system.md and prompts/reviewer_system.md.
Architecture (v0.3)
User opens Claude Code in VSCode
↓
/draft <topic> ← you (Claude) write the paper using prompts/
↓
/codex-review ← you invoke codex exec via Bash (subprocess)
↓ (Codex reviews independently, process-isolated)
/iterate ← you read Codex's review, revise, then re-trigger Codex
↓
/claim-check ← you and Codex score the same claims with the same prompt, then compare
↓
/finalize ← you produce DOCX + cover letter + citation placeholders
The five slash commands live in .claude/commands/, each documenting its own steps, inputs, and outputs.
Your role
You are the writer agent. Codex is the independent reviewer agent (invoked via codex exec subprocess, cannot see your prompt).
You never review your own writing — reviewing is Codex's job. Crossing that line collapses the project's core "independent review" claim.
Priorities
- Working > perfect — get the chain from
/draftto/finalizeflowing end-to-end before polishing any single step. - Real data > template fill — Results section numbers must come from
my-paper/data/analysis_results.json. Never fabricate. - Cautious wording > overclaim — default to "is consistent with"; let Codex's review decide whether stronger phrasing is justified.
- File interface > in-process communication — the only channel between Claude and Codex is markdown files on disk (
draft.md/review_round_N.md). - S/N yardstick > field-journal leniency — even when the user targets GRL/ACP, tighten to S/N: every number paired with effect size + 95% CI + n + test name + precise p (Reporting Summary); abstract first sentence delivers broad significance; refs ≤ 50; displays ≤ 5.
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 · 149 lines · 1,975 tokens per session scan A a313da8acf10
dual-ai-paper-coach CLAUDE.md is an instructions file published in the GitHub repository dengxu11111/dual-ai-paper-coach (12 stars, last pushed 4mo ago), licensed MIT. It adds 1,975 tokens to every session, about $0.0099 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-30.
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).