Borrowing it
Nothing to install: this file belongs to Rezenders/scientific_writing_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/Rezenders/scientific_writing_agent/main/CLAUDE.mdgit clone --depth 1 https://github.com/Rezenders/scientific_writing_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/rezenders/scientific_writing_agent/claude-md)<a href="https://agentmods.dev/instructions/rezenders/scientific_writing_agent/claude-md"><img src="https://agentmods.dev/badge/instructions/rezenders/scientific_writing_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.01784 | $0.01784 |
| Opus 5 | $0.00892 | $0.00892 |
| Sonnet 5 | $0.00357 | $0.00357 |
| Haiku 4.5 | $0.00178 | $0.00178 |
Grade D, and why
scientific_writing_agent CLAUDE.md scanned grade D with 2 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- CUSTOMIZE: Add any project-specific terminology rules here. Example: - "Action" has three distinct meanings in this manuscript: [explain]. Keep them distinct. - Refer to the system's reasoning component as "reasoner Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
Install: sudo apt install latexmk chktex ... How it starts
The opening of the file, as written. The whole thing — 244 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 when working with code in this repository.
What This Is
This repository contains the LaTeX source for "[Paper Title]". A research paper on [topic]. The paper targets [journal/conference format].
The goal is to produce a technically rigorous, internally consistent, publication-ready scientific manuscript. Edits must improve clarity, precision, coherence, and argument strength without changing the intended technical meaning.
Research questions (anchor for consistency checks):
- RQ1: [Your first research question]
- RQ2: [Your second research question]
Writing Objectives
Prioritize, in this order:
- Technical correctness
- Consistency with the rest of the manuscript
- Clarity and precision
- Concise academic style
- Grammar and fluency
Do not make stylistic changes that weaken technical precision.
Writing Style
- Use formal scientific English.
- Prefer precise terminology over stylistic variation.
- Prefer direct, declarative sentences.
- When introducing a tool or system, prefer "This work uses X" over "X serves as Y" — keep the authors as the active agent.
- When introducing a contribution, prefer "This work proposes X to achieve Y" — make clear it is a contribution of this paper.
- Avoid conversational wording, promotional tone, and vague intensifiers.
- Avoid vague relative clauses that restate a role without adding information.
- Avoid redundancy across adjacent sentences and paragraphs.
- Avoid introducing new terminology when existing terminology already covers the concept.
- Preserve the manuscript's established terminology unless there is a strong reason to change it.
- Preserve the intended meaning of claims, definitions, assumptions, and results.
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 · 244 lines · 1,784 tokens per session scan D a56b36fe3d82
scientific_writing_agent CLAUDE.md is an instructions file published in the GitHub repository Rezenders/scientific_writing_agent (11 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 1,784 tokens to every session, about $0.0089 per session on Opus 5. A static security scan graded it D with 2 findings (hidden instructions, asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
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).
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.
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).
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.