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 pre-submissiongit 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/pre-submission)<a href="https://agentmods.dev/skills/rezenders/scientific_writing_agent/pre-submission"><img src="https://agentmods.dev/badge/skills/rezenders/scientific_writing_agent/pre-submission/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/pre-submission"><img src="https://agentmods.dev/badge/skills/rezenders/scientific_writing_agent/pre-submission.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.00037 | $0.00613 |
| Opus 5 | $0.00018 | $0.00307 |
| Sonnet 5 | $0.00007 | $0.00123 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
pre-submission 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 11d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Submission Checklist
Structured go/no-go pipeline before submitting the manuscript. Run every step in order — do not skip steps even if earlier ones pass.
Steps
1. Build + Lint
Invoke the /paper-build skill.
- Pass: PDF builds without errors and lint is clean.
- Fail: Report all errors and warnings from
/paper-build. Stop and fix build errors before continuing; lint warnings may be addressed in parallel.
3. Open Annotations
Invoke the /find-annotations skill.
- Pass: Zero open annotations in active
.texfiles. - Fail: List all open annotations. Flag
\todoand\redas blocking;\reviseand author comments as non-blocking unless they indicate unresolved technical questions.
4. Consistency Audit
Invoke consistency-auditor for a full manuscript audit.
Ask: "Perform a full consistency audit across all active section files. Focus on: terminology drift, acronym consistency, contribution-statement alignment, and cross-section contradictions."
- Pass: No critical inconsistencies.
- Fail: Report all critical and medium-priority findings.
5. Implementation Alignment Spot-Check (OPTIONAL)
Invoke paper-implementation-checker on the highest-risk claims in the paper (typically 2–3):
- Core type/schema descriptions
- Interface method names cited in the paper
- Running examples in the evaluation or results section
Ask each: "Does this description match the current implementation? Report CONSISTENT / DIVERGES / CANNOT_VERIFY."
- Pass: All CONSISTENT.
- Fail: Report divergences. Do not silently update either side — flag for author decision.
Final Report Format
## Pre-Submission Report
| Step | Status | Notes |
|---|---|---|
| Build | PASS / FAIL | |
| Lint | PASS / FAIL | N warnings |
| Annotations | PASS / FAIL | N open |
| Consistency | PASS / FAIL | N critical issues |
| Implementation | PASS / SKIP / FAIL | N divergences |
### Verdict: GO / NO-GO
**Blocking issues** (must fix before submission):
- ...
**Non-blocking notes** (address if time allows):
- ...
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.
- 11d ago First seen · 85 lines · 37 tokens per session scan A 1b5dccb8ce77
pre-submission is a skill published in the GitHub repository Rezenders/scientific_writing_agent (11 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 613 once invoked, about $0.0002 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 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
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for 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
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
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.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…