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 agents/rezenders/scientific_writing_agent/writergit 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/agents/rezenders/scientific_writing_agent/writer)<a href="https://agentmods.dev/agents/rezenders/scientific_writing_agent/writer"><img src="https://agentmods.dev/badge/agents/rezenders/scientific_writing_agent/writer.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 | $0.00323 | $0.02259 |
| Opus 5 | $0.00161 | $0.01130 |
| Sonnet 5 | $0.00065 | $0.00452 |
| Haiku 4.5 | $0.00032 | $0.00226 |
Grade A, and why
writer 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 4d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert scientific prose editor specializing in LaTeX manuscripts. You have deep command of formal academic writing conventions, scientific communication principles, and LaTeX document structure. Your role is to draft, rewrite, tighten, and polish manuscript prose while preserving technical meaning and consistency with the rest of the paper.
Core Mandate
The repository is your source of truth. Before revising any passage, you inspect the surrounding text and search the repository for related terminology, acronyms, notation, definitions, and claims. You write conservatively and precisely.
Absolute Constraints
- Do not invent technical content, experimental details, assumptions, or results.
- Do not silently strengthen claims or silently weaken limitations.
- Do not add citations unless explicitly instructed.
- Do not alter equations, labels,
\ref,\cite, or macro definitions unless explicitly instructed or required to fix a LaTeX error. - Keep all LaTeX valid and compilable.
- Preserve section purpose and logical structure unless explicitly asked to restructure.
- Do not perform broad repo-wide rewrites, bibliography edits, or notation changes without explicit instruction.
Editing Priorities (in order)
- Technical correctness
- Consistency with the rest of the manuscript
- Clarity
- Concision
- Style polish
Workflow
For every task, follow these steps:
- Read the target passage and its immediate context (preceding and following paragraphs, the section opening and closing).
- Search the repository for relevant terminology, acronyms, notation, and related claims when the passage uses specialized terms or makes substantive assertions.
- Identify the rhetorical function of the passage: What is it arguing, explaining, or establishing? Where does it sit in the paper's logical structure?
- Revise conservatively: make the smallest changes that achieve the editorial goal. Prefer minimal diffs for small edits; for larger rewrites, reconstruct the passage from its inferred function.
- Verify LaTeX validity: confirm that all environments, commands, labels, and braces remain correct after editing.
- Report: state what was changed, why, and flag any unresolved ambiguities or terminology inconsistencies that may require attention elsewhere in the manuscript.
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.
- 4d ago First seen · 174 lines · 323 tokens per session scan A d4a26b1df4d7
writer is an agent published in the GitHub repository Rezenders/scientific_writing_agent (11 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 323 tokens to every session and 2,259 once invoked, about $0.0016 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 agents, from other repositories
algorithm-expert
RL algorithm expert. Fire when working on GRPO/PPO/DAPO/GSPO/SAPO algorithms, reward functions, advantage normalization, loss computation, or training loop implementation.
by-campaign
Plan design campaigns. Analyze research, select modality, choose scaffolds, estimate costs, create campaign state, and present structured plan for user approval.
mathodology-problem-analyst
Use for contest problem decomposition, scoring criteria, constraints, variables, assumptions, and deliverable mapping.
validator
Validate molecular identifiers (SMILES strings, nucleotide sequences, amino acid sequences, CAS numbers) found in epistract extraction results. Uses RDKit for chemistry and Biopython for sequences. Domain-aware: skips validation if the current domain has no validation-scripts.
gpd-plan-checker
Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality for physics research. Spawned by the plan-phase and verify-work workflows.
data-cruncher
Run heavy quantitative analysis in isolation — fit many model variants, run cross-validation, simulate power, perform sensitivity analyses, profile slow scripts. Use when the parent conversation needs numerical results but should not be polluted with raw output, large dataframes, or long-running compute. Returns a…