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 skills add Rezenders/scientific_writing_agent --skill argument-plangit 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/skills/rezenders/scientific_writing_agent/argument-plan)<a href="https://agentmods.dev/skills/rezenders/scientific_writing_agent/argument-plan"><img src="https://agentmods.dev/badge/skills/rezenders/scientific_writing_agent/argument-plan/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/skills/rezenders/scientific_writing_agent/argument-plan"><img src="https://agentmods.dev/badge/skills/rezenders/scientific_writing_agent/argument-plan.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.00025 | $0.00731 |
| Opus 5.5 | $0.00010 | $0.00292 |
| Sonnet 5.5 | $0.00005 | $0.00146 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
argument-plan 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 27d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Argument Plan
Read-only planning workflow. Use this skill to turn an author-controlled passage contract into an inspectable argument structure before drafting. Do not write polished manuscript prose and do not edit files.
When To Use
Use when:
- a passage has a nontrivial rhetorical function;
- the author has specified intent but not paragraph structure;
- a reviewer response requires careful positioning before prose is drafted;
- a section transition, contribution framing, limitation, or results interpretation could overclaim;
/write-to-intentreaches its “Confirm The Argument” step and the structure is not already explicit.
Do not use for minor wording fixes or straightforward local edits.
Required Inputs
Require a passage contract based on .agents/context/passage-contract.md, including at least:
- rhetorical function;
- required scientific content and evidence;
- prohibited claims or implications;
- relevant neighboring context;
- target length or structural constraints when known.
If any missing field would materially change the argument, ask the author before planning.
Reference Context
Read only what is needed:
.agents/context/passage-contract.md.agents/context/claim-ledger.mdfor high-risk evidence boundaries.agents/context/do-not-say.mdfor prohibited overclaims.agents/context/terminology.mdfor canonical terms.agents/context/contributions.mdfor contribution alignment.agents/context/evaluation-claims.mdfor evaluation-result scope- target passage and immediate neighboring manuscript text
For implementation-dependent claims, request or perform a targeted .agents/agents/paper-implementation-checker.md pass before planning.
Workflow
- Check the contract. Identify missing or ambiguous scientific content, evidence, scope conditions, and prohibited claims.
- Map evidence to claims. For each required point, record the manuscript, result, implementation, or citation basis that permits it.
- Build the argument skeleton. Produce a claim-level structure, not prose. Each step should state:
- role in the passage;
- claim or transition;
- evidence/source;
- allowed inference;
- prohibited overextension.
- Check local flow. Explain how the skeleton connects to the preceding and following text.
- Ask for approval. Stop and ask the author to approve, reject, or modify the skeleton before any drafting skill is used.
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.
- 27d ago First seen · 91 lines · 25 tokens per session scan A ef9c0a6bfe46
argument-plan is a skill published in the GitHub repository Rezenders/scientific_writing_agent (14 stars, last pushed 28d ago), licensed Apache-2.0. It adds 25 tokens to every session and 731 once invoked, about $0.0001 per session on Opus 5.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-09-21.
Other skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
exploratory-data-analysis
Performs bounded, local exploratory analysis of explicitly supported scientific files. Supports redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
matlab
Builds, reviews, migrates, and plans MATLAB or GNU Octave numerical workflows. Use for arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
phylogenetics
Builds and analyzes phylogenetic trees using MAFFT multiple sequence alignment, IQ-TREE maximum likelihood with ModelFinder and branch support, and FastTree approximate inference. Uses ETE3 for tree summaries and visualization. Applies to homologous nucleotide or protein sequences, microbial gene trees, protein…
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
presenting-conference-talks
Generates conference presentation slides (Beamer LaTeX PDF and editable PPTX) from a compiled paper with speaker notes and talk script. Use when preparing oral talks, spotlight presentations, or invited talks for ML and systems conferences.