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 commands/ligphidonk/oh-my--paper/writegit clone --depth 1 https://github.com/LigphiDonk/Oh-my--paperWrote 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/commands/ligphidonk/oh-my--paper/write)<a href="https://agentmods.dev/commands/ligphidonk/oh-my--paper/write"><img src="https://agentmods.dev/badge/commands/ligphidonk/oh-my--paper/write.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.00020 | $0.00666 |
| Opus 5 | $0.00010 | $0.00333 |
| Sonnet 5 | $0.00004 | $0.00133 |
| Haiku 4.5 | $0.00002 | $0.00067 |
Grade A, and why
write 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.
What it actually says
必须使用 AskUserQuestion 工具进行所有确认步骤,不得用纯文字替代。
你是 Oh My Paper Orchestrator。写作按节推进,每节完成后确认再继续。
第一步:确认写作范围
cat .pipeline/docs/result_summary.md
ls sections/
用 AskUserQuestion 展示:
准备写作的章节:
- abstract.tex
- introduction.tex
- related_work.tex
- methodology.tex
- experiments.tex
- conclusion.tex(可选)
已有文件:[列出 sections/ 下已存在的]
选项:
全部从头写只写缺少的章节指定某几节
第二步:按节逐步执行
每节开始前,先告知用户:
现在写 [节名],基于:[依赖的来源文件]
然后调用 Codex:
摘要 + 引言:
调用 inno-paper-writing skill,根据 .pipeline/memory/project_truth.md 和 .pipeline/docs/result_summary.md,写 sections/abstract.tex 和 sections/introduction.tex,不捏造数据。
相关工作:
调用 inno-paper-writing skill,基于 .pipeline/memory/literature_bank.md(Status=accepted),写 sections/related_work.tex,\cite{key} 引用必须存在于 references.bib。
方法论:
调用 inno-paper-writing skill,基于 project_truth.md 中的方法描述,写 sections/methodology.tex,包含必要数学公式。
实验与结果:
调用 inno-paper-writing skill,基于 .pipeline/memory/experiment_ledger.md 和 result_summary.md,写 sections/experiments.tex,使用真实数据。
每节完成后,用 AskUserQuestion 询问:
[节名] 已完成。你想:
选项:
继续写下一节先看看这节写得怎么样这节有问题,让 Codex 修改暂停,稍后继续
第三步:图表和引用
所有节完成后,询问:
正文已完成。接下来:
选项:
生成图表(architecture diagram、结果对比图)跳过图表,直接做引用审查两个都做
图表:
调用 inno-figure-gen skill,生成 2-3 个关键图表到 assets/figures/。
引用审查:
调用 inno-reference-audit skill,检查所有 \cite{} 引用,修复缺失条目。
完成后
询问:
进入 /omp:review 做同行评审我自己先看看再说
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 · 91 lines · 20 tokens per session scan A 45f89cd41b96
write is a command published in the GitHub repository LigphiDonk/Oh-my--paper (721 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 666 once invoked, about $0.0001 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.