Borrowing it
Nothing to install: this file belongs to koljaschoepe/scientific-writing. 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/koljaschoepe/scientific-writing/main/.claude/skills/rewrite/SKILL.mdgit clone --depth 1 https://github.com/koljaschoepe/scientific-writingWrote 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/koljaschoepe/scientific-writing/rewrite)<a href="https://agentmods.dev/skills/koljaschoepe/scientific-writing/rewrite"><img src="https://agentmods.dev/badge/skills/koljaschoepe/scientific-writing/rewrite/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/koljaschoepe/scientific-writing/rewrite"><img src="https://agentmods.dev/badge/skills/koljaschoepe/scientific-writing/rewrite.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.00031 | $0.00453 |
| Opus 5 | $0.00015 | $0.00227 |
| Sonnet 5 | $0.00006 | $0.00091 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
rewrite 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 9d 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.
What it actually says
Kapitel neu schreiben
Verwirft den bestehenden Text eines Kapitels und schreibt es komplett neu.
Ablauf
1. Kapitelnummer bestimmen
Mit Parameter (z.B. /rewrite 2.3):
- Verwende die angegebene Kapitelnummer
Ohne Parameter:
- Frage: "Welches Kapitel soll neu geschrieben werden? (z.B. 2.3)"
2. Sicherheitsabfrage
Prüfe ob das Kapitel bereits existiert:
Falls in final/: "Kapitel [X.X] ist bereits freigegeben. Wenn du es neu schreibst, wird die freigegebene Version archiviert. Bist du sicher?"
Falls in draft/: "Kapitel [X.X] hat einen Entwurf. Dieser wird überschrieben. Bist du sicher?"
Falls nicht vorhanden: "Kapitel [X.X] wurde noch nicht geschrieben. Nutze /write [X.X] stattdessen."
3. Bestehenden Text archivieren
Falls eine Version existiert:
- Benenne die Datei um:
[X-X].md->[X-X].bak.md(im gleichen Ordner) - Melde: "Vorherige Version gesichert als [X-X].bak.md"
4. Neu schreiben
Starte den Agent .claude/agents/writer.md für das Kapitel.
Der Agent folgt dem bestehenden Plan (es sei denn, der Plan wurde auch geändert).
5. Ergebnis
Kapitel [X.X] wurde neu geschrieben.
Vorherige Version: output/phase-05-writing/[draft|final]/[X-X].bak.md
Neue Version: output/phase-05-writing/draft/[X-X].md
Wörter: [Y] (vorher: [Z])
Prüfe das Ergebnis und nutze /approve um es freizugeben.
Falls die neue Version schlechter ist, kannst du die Backup-Datei
wiederherstellen.
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.
- 9d ago First seen · 59 lines · 31 tokens per session scan A 856ce20dbfad
rewrite is a skill published in the GitHub repository koljaschoepe/scientific-writing (11 stars, last pushed 23d ago), licensed MIT. It adds 31 tokens to every session and 453 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
ml-paper-writing
Write publication-ready ML/AI papers for NeurIPS, ICML, ICLR, ACL, AAAI, COLM. Use when drafting papers from research repos, structuring arguments, verifying citations, or preparing camera-ready submissions. Includes LaTeX templates, reviewer guidelines, and citation verification workflows.
academic-plotting
Generates publication-quality figures for ML papers from research context. Given a paper section or description, extracts system components and relationships to generate architecture diagrams via Gemini. Given experiment results or data, auto-selects chart type and generates data-driven figures via matplotlib/seaborn.…
systems-paper-writing
Comprehensive guide for writing systems papers targeting OSDI, SOSP, ASPLOS, NSDI, and EuroSys. Provides paragraph-level structural blueprints, writing patterns, venue-specific checklists, reviewer guidelines, LaTeX templates, and conference deadlines. Use this skill for all systems conference paper writing.
paperjury
A tool for reviewing and editing computer-science conference papers in LaTeX or Markdown, the document formats commonly used for research papers. It supports direct edits, structured pre-submission review, and an optional unattended mode for selected fixes.
overleaf
Sync and manage Overleaf LaTeX projects from the command line. Pull projects locally, push changes back, compile PDFs, and download compile outputs like .bbl files for arXiv submissions. Use when working with LaTeX, Overleaf, academic papers, or arXiv.
parallel-subagents
When a task decomposes into independent slices — separate files, OR separate sections of ONE file — fan it out: write job files to the subagent queue and the host runs real parallel Codex workers for you. For a single file, extract per-section slice files into the queue's work/ zone, let workers polish them in…