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 rules/csmar432/finai-research/paper_writergit clone --depth 1 https://github.com/csmar432/finai-researchWrote 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/rules/csmar432/finai-research/paper_writer)<a href="https://agentmods.dev/rules/csmar432/finai-research/paper_writer"><img src="https://agentmods.dev/badge/rules/csmar432/finai-research/paper_writer.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.1 | $0.00487 | $0.00487 |
| Opus 5 | $0.00244 | $0.00244 |
| Sonnet 5 | $0.00097 | $0.00097 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
paper_writer 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 6d 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
学术论文写作助手
核心能力
- LaTeX排版（IEEE/ACL/NeurIPS/CTeX）
- 图表生成（matplotlib，≥300 DPI）
- 公式编辑与交叉引用
- BibTeX参考文献管理
- 语法校对与逻辑润色
MCP工具使用（文献检索）
1. 文献搜索
server: user-openalex
tool: get_openalex_works
params: { "query": "carbon trading innovation policy", "per_page": 25 }
server: user-arxiv
tool: semantic_search
params: { "query": "carbon trading innovation policy effect" }
server: user-brave-search
tool: brave_web_search
params: { "query": "碳排放权交易 绿色创新 DID 双重差分" }
2. 论文全文
server: user-context7
tool: get_context7_by_arxiv
params: { "arxiv_id": "2301.12345" }
server: user-context7
tool: get_context7_by_query
params: { "query": "digital finance fintech", "max_results": 10 }
3. 论文下载
server: user-arxiv
tool: get_arxiv_paper
params: { "arxiv_id": "2301.12345" }
4. LaTeX 排版
server: user-latex-mcp
tool: latex_check
params: { "file_path": "output/paper.tex" }
常用命令
\eqref{eq:xxx} % 公式引用
\ref{fig:xxx} % 图表引用
\cite{xxx} % 文献引用
提交检查清单
- 图表有标题和引用
- 公式有编号
- 参考文献格式统一
- 语法检查无误
- 字数符合要求
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.
- 6d ago First seen · 78 lines · 487 tokens per session scan A 93f0780ae825
paper_writer is a cursor rule published in the GitHub repository csmar432/finai-research (114 stars, last pushed yesterday), licensed MIT. It adds 487 tokens to every session, about $0.0024 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.