Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/rezenders/scientific_writing_agent/agents-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/agents-md)<a href="https://agentmods.dev/instructions/rezenders/scientific_writing_agent/agents-md"><img src="https://agentmods.dev/badge/instructions/rezenders/scientific_writing_agent/agents-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.01705 | $0.01705 |
| Opus 5 | $0.00852 | $0.00852 |
| Sonnet 5 | $0.00341 | $0.00341 |
| Haiku 4.5 | $0.00170 | $0.00170 |
Grade A, and why
scientific_writing_agent 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 5d 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to Codex 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.
- 5d ago First seen · 244 lines · 1,705 tokens per session scan A 61779c3952db
scientific_writing_agent AGENTS.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,705 tokens to every session, about $0.0085 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
bio-gene-to-reference-tree copilot-instructions.md
Copilot instructions for Hongda-Zhao/bio-gene-to-reference-tree, a project described as: Auditable agent skill for resolving protein queries, selecting references, and planning reproducible phylogenetic trees.
braina GEMINI.md
Instructions for brainets/braina, covering project: braina (brain interaction analysis), 1. project context & purpose, 2. commands, verify environment (all core dependencies) and run the verification test suite for frites + hoi.
research-automation CLAUDE.md
Instructions for lucafusarbassini/research-automation, covering ricet - research automation framework, project overview, claude-flow mcp, workflow habits and file organization.
shannon-prover CLAUDE.md
Claude Code instructions for SkyShannonProver/shannon-prover, covering shannon prover: claude entry point, current boundary, easycrypt environment, eval safety and current documentation.
SciCrucible CLAUDE.md
Claude Code instructions for Xinyang-Li666/SciCrucible, covering 科学知识库, 知识库结构, 可用命令, 项目目录 and 工作原则.
torchcell CLAUDE.md
Claude Code instructions for Mjvolk3/torchcell, covering vision -- the virtual cell (north star), for local configs, git worktrees, programming guide and provenance & reproducibility.