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 skills/ai4paper/apaper-plugin/writingnpx skills add ai4paper/apaper-plugin --skill writinggit clone --depth 1 https://github.com/ai4paper/apaper-pluginWrote 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/ai4paper/apaper-plugin/writing)<a href="https://agentmods.dev/skills/ai4paper/apaper-plugin/writing"><img src="https://agentmods.dev/badge/skills/ai4paper/apaper-plugin/writing.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.00139 | $0.01153 |
| Opus 5 | $0.00069 | $0.00576 |
| Sonnet 5 | $0.00028 | $0.00231 |
| Haiku 4.5 | $0.00014 | $0.00115 |
Grade A, and why
writing 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 3d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Academic Writing
Help the user turn rough academic prose into clear, publication-ready writing without changing the technical meaning. Preserve the author's intended meaning while meeting publication standards.
Goals
- Preserve the author's claims, evidence, and intended emphasis.
- Improve clarity, rigor, concision, and logical flow.
- Prefer neutral, evidence-driven phrasing over promotional language.
- Keep the result LaTeX-ready when the user is working in
.texfiles.
When Working
First identify what kind of help the user wants:
- polish a sentence or paragraph
- rewrite a full section
- align a manuscript with a target venue's tone
- improve structure and flow
- tighten claims for technical accuracy
- make LaTeX prose cleaner and more consistent
Match the depth of the response to the request. If the user asks for a direct rewrite, give the rewrite first. If the user asks for critique, explain the issues first and then propose fixes.
Rule Sets
The writing rules are split by concern. Always apply PRINCIPLES.md; apply the others when the task calls for them.
| File | When to apply |
|---|---|
| PRINCIPLES.md | Always. Core prose principles, sentence flow, editing heuristics, safeguards, and self-review. |
| JOURNAL.md | Journal or IEEE-style manuscripts — even if the user never says "IEEE." Venue tone, section and contribution-list templates, writing about figures/tables/equations, structure checks. |
| THEOREMS.md | Polishing the formal statement of a theorem, lemma, or proposition — the cited block, not its proof. Statement structure, ordering, and notation. |
| LATEX.md | The user is editing a LaTeX manuscript or *.bib file. LaTeX and BibTeX conventions, including figure, table, and equation typesetting and automatic numbering. |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 103 lines · 139 tokens per session scan A 2893cd03a59b
writing is a skill published in the GitHub repository ai4paper/apaper-plugin (3 stars, last pushed 10d ago), licensed MIT. It adds 139 tokens to every session and 1,153 once invoked, about $0.0007 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-31.
Other skills, from other repositories
codex-setup
Initialize sd0x-dev-flow infrastructure for Codex CLI and other non-Claude agents. Generates AGENTS.md, installs the commit-msg hook, copies runner scripts. The pre-push gate is opt-in via --with-push-gate. Use when setting up a new project or after updating skills.
debug
Interactive debugging workflow with hypothesis-driven probe loop. Use when: unknown bugs, script errors, silent failures, troubleshooting. Not for: known bugs (use bug-fix), GitHub issue analysis (use issue-analyze), code understanding (use code-explore). Output: debug report with probe journal + root cause + fix.
feature-dev
Feature development workflow. Use when: implementing features, writing code, running dev loop. Not for: understanding code (use code-explore), reviewing code (use codex-code-review). Output: implemented feature + tests + review gate.
codex-implement
Implement features via Codex MCP. Use when: writing new code from specs, implementing features, Codex-driven development. Not for: code review (use codex-code-review), architecture advice (use codex-architect). Output: implemented code + review loop.
doc-refactor
Refactor documents — simplify without losing information, visualize flows with sequenceDiagram.
invest
First-time fork users: run the invest-setup skill first to initialize. The main flow lives in this skill (the AI agent uses the CLI/MCP to view the portfolio / run the committee / replay decision history). The Web GUI has been retired (2026-07) — every capability is exposed via CLI subcommands / MCP tools. The backend…