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 zhousodo/paper-submission-check --skill paper-english-polishinggit clone --depth 1 https://github.com/zhousodo/paper-submission-checkWrote 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/zhousodo/paper-submission-check/paper-english-polishing)<a href="https://agentmods.dev/skills/zhousodo/paper-submission-check/paper-english-polishing"><img src="https://agentmods.dev/badge/skills/zhousodo/paper-submission-check/paper-english-polishing/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/zhousodo/paper-submission-check/paper-english-polishing"><img src="https://agentmods.dev/badge/skills/zhousodo/paper-submission-check/paper-english-polishing.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.00106 | $0.05746 |
| Opus 5 | $0.00053 | $0.02873 |
| Sonnet 5 | $0.00021 | $0.01149 |
| Haiku 4.5 | $0.00011 | $0.00575 |
Grade A, and why
paper-english-polishing 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 12d 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 — 494 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Academic English Polishing
Paragraph-level polishing for academic papers targeting top-tier venues (IEEE S&P, USENIX Security, NeurIPS, ICML, TDSC, TIFS, etc.). Handles both Chinese-to-English translation and English-to-English refinement.
Relationship to paper-submission-check: That skill detects issues; this skill rewrites text. Run this skill first (polishing), then run paper-submission-check (validation).
Execution Safety [CRITICAL]
Before any rewrite, lock these invariants:
- Never change technical facts: numbers, theorem statements, equations, symbols, citations, table/figure references.
- Never invent claims, datasets, baselines, or citations that are not in source text.
- Preserve author intent; when wording is ambiguous, keep a conservative rewrite and flag a question.
- Preserve all LaTeX commands and labels (
\label{},\ref{},\cite{}) exactly unless user explicitly asks to refactor LaTeX. - Chinese comments are allowed: LaTeX comments (
% 中文注释) may remain in Chinese — they are invisible in PDF and serve as author notes. Do NOT translate or remove them unless the author explicitly requests it. - Chinese in
\zhpara{}/\zhcaption{}is preserved: These are part of the bilingual comparison scaffolding and are hidden by\showchinesefalsebefore submission.
Workflow
Polishing Progress:
- [ ] Phase 0: Pre-Analysis (scope lock, language, venue, terminology, bilingual scaffolding)
- [ ] Phase 0s: Structural Replacement (title, theorem names, keywords, TikZ labels, table headers, algorithm text, pgfplots labels — direct EN replacement, no bilingual pairing)
- [ ] Phase 1: Title & Abstract
- [ ] Phase 2: Introduction
- [ ] Phase 3: Related Work
- [ ] Phase 4: Method / Approach
- [ ] Phase 5: Experiments / Evaluation
- [ ] Phase 6: Discussion / Limitations
- [ ] Phase 7: Conclusion
- [ ] Phase 8: Appendix (if any)
- [ ] Phase 9: Cross-Section Consistency Verification
- [ ] Phase 10: Final AI-Style Sweep
- [ ] Phase 11: Submission Toggle (set \showchinesefalse, verify zero Chinese in PDF)
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.
- 12d ago First seen · 494 lines · 106 tokens per session scan A b942a8f25de4
paper-english-polishing is a skill published in the GitHub repository zhousodo/paper-submission-check (24 stars, last pushed 4mo ago), licensed MIT. It adds 106 tokens to every session and 5,746 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…