Borrowing it
Nothing to install: this file belongs to zhnnky329/MathModeling-skills. 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/zhnnky329/MathModeling-skills/main/.claude/skills/paper-polisher/SKILL.mdgit clone --depth 1 https://github.com/zhnnky329/MathModeling-skillsWrote 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/zhnnky329/mathmodeling-skills/paper-polisher)<a href="https://agentmods.dev/skills/zhnnky329/mathmodeling-skills/paper-polisher"><img src="https://agentmods.dev/badge/skills/zhnnky329/mathmodeling-skills/paper-polisher/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/zhnnky329/mathmodeling-skills/paper-polisher"><img src="https://agentmods.dev/badge/skills/zhnnky329/mathmodeling-skills/paper-polisher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 198 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00041 | $0.02986 |
| Opus 5 | $0.00020 | $0.01493 |
| Sonnet 5 | $0.00008 | $0.00597 |
| Haiku 4.5 | $0.00004 | $0.00299 |
Grade A, and why
paper-polisher 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 13d 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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Polish mathematical modeling contest paper sections for language quality, logical clarity, formula consistency, and claim calibration.
This skill operates on already-drafted paper sections. It improves wording, fixes grammar, checks formulas, calibrates hedging to match evidence strength, detects overclaims, and ensures formatting compliance. It does not invent new content, add unsupported claims, or rewrite the paper's scientific argument.
Adapted from nature-polishing design principles: language serves the argument, polish should not hide weak reasoning, and claims must be proportional to evidence.
This skill does not write new paper sections, run experiments, generate figures, or perform final QA.
When to use
Use this skill:
- After
paper-section-writerhas drafted one or more paper sections. - Before
quality-assurance-auditor. - When the user says: "polish the paper", "check the English", "fix the grammar", "improve the writing", "calibrate the claims", "check for overclaims", "proofread Q1 section".
- When Chinese-to-English translation has produced rough drafts that need smoothing.
- When formulas, notation, or terminology are inconsistent across sections.
Preconditions
The following should already exist or be provided:
- Paper section drafts under
paper/sections/. - Final method explanations (for formula and notation verification).
- Final result analyses (for claim verification).
- The global symbol table at
planning/symbol_table.md(if available). - Contest formatting requirements (if available).
If paper sections do not exist, hand back to paper-section-writer.
Inputs
Use or request:
paper/sections/*.mdorpaper/sections/*.tex— the drafted sections.methods/Qx/qx_final_method_explanation.md— for formula and notation verification.results/Qx/reports/qx_final_result_analysis.md— for claim verification.planning/symbol_table.md— for notation consistency.- Contest formatting requirements.
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.
- 13d ago First seen · 281 lines · 41 tokens per session scan A 3a26bbf5662b
paper-polisher is a skill published in the GitHub repository zhnnky329/MathModeling-skills (882 stars, last pushed 18d ago), licensed MIT. It adds 41 tokens to every session and 2,986 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
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…