Borrowing it
Nothing to install: this file belongs to yunshenwuchuxun/latex-paper-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/yunshenwuchuxun/latex-paper-skills/main/.codex/skills/latex-rhythm-refiner/SKILL.mdgit clone --depth 1 https://github.com/yunshenwuchuxun/latex-paper-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/yunshenwuchuxun/latex-paper-skills/latex-rhythm-refiner)<a href="https://agentmods.dev/skills/yunshenwuchuxun/latex-paper-skills/latex-rhythm-refiner"><img src="https://agentmods.dev/badge/skills/yunshenwuchuxun/latex-paper-skills/latex-rhythm-refiner/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/yunshenwuchuxun/latex-paper-skills/latex-rhythm-refiner"><img src="https://agentmods.dev/badge/skills/yunshenwuchuxun/latex-paper-skills/latex-rhythm-refiner.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.00037 | $0.00792 |
| Opus 5 | $0.00018 | $0.00396 |
| Sonnet 5 | $0.00007 | $0.00158 |
| Haiku 4.5 | $0.00004 | $0.00079 |
Grade A, and why
latex-rhythm-refiner 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LaTeX Rhythm Refiner
When to Use
- After LaTeX content generation is complete
- To improve prose flow and readability in academic documents
- When sections feel monotonous or blocky
When NOT to Use
- During initial content drafting
- For citation verification or addition
- For technical/structural LaTeX fixes
Core Principles
1. Preserve Citations Exactly
- Every
\cite{...}must remain in place - Citations stay attached to their original semantic context
- Never move a citation to a different claim or sentence meaning
2. Vary Rhythm Stochastically
Sentence length: Mix short (5-12 words), medium (13-22 words), and long (23-35 words) sentences. Avoid consecutive sentences of similar length.
Paragraph length: Alternate between:
- Short (2-3 sentences) for emphasis or transitions
- Medium (4-5 sentences) for standard exposition
- Long (6-8 sentences) for complex arguments
3. Remove Fillers
Eliminate or replace:
- "in order to" → "to"
- "it is worth noting that" → (delete or rephrase directly)
- "due to the fact that" → "because"
- "in the context of" → "in" or "for"
- "a large number of" → "many"
- "in spite of the fact that" → "although"
- "at the present time" → "now" or "currently"
- "for the purpose of" → "to" or "for"
4. Minimize Transitions
Remove when structure already implies the relationship:
- "However," / "Therefore," / "Moreover," / "Furthermore,"
- "As mentioned above," / "As previously discussed,"
- "It should be noted that" / "In this regard,"
5. Tighten Prose
- Prefer active voice; replace vague verbs ("shows", "does", "works") with concrete ones
- Avoid repeated sentence openings across adjacent sentences ("This", "In practice", etc.)
- Replace hedge stacks ("may potentially") with one qualifier
- Each paragraph: one main idea, clear first sentence
- Ensure figures/tables are referenced and explained in text
Processing Workflow
Per-Section Refinement
Process one section at a time:
- Read the section fully to understand context and argument flow
- Identify all
\cite{...}locations and their attached claims - Map current sentence/paragraph lengths
- Refine:
- Vary sentence lengths (break long chains, combine choppy sequences)
- Adjust paragraph boundaries for rhythm
- Strip fillers and unnecessary transitions
- Verify all citations remain with their original semantic claims
- Output the refined section
What ships with it
1 file 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 · 91 lines · 37 tokens per session scan A 4b4bccd70040
latex-rhythm-refiner is a skill published in the GitHub repository yunshenwuchuxun/latex-paper-skills (259 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 792 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
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…