tex-render

tex-render is a skill for Claude Code from LFTPadilla/agent-dev-kit. It costs 63 tokens per session (1,440 once invoked), scanned A, original, MIT.

A converter that turns LaTeX, a text format for mathematical formulas, into image files such as PNG, JPEG, WebP, AVIF, or SVG.

In plain words
What is it for?
It is for rendering formulas, equations, and mathematical notation as images.
Why use it?
It makes equations viewable as graphics when raw formula text is not suitable.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node <skill_folder>/scripts/render.js --format jpeg --quality 80 '\frac{F}{m}=a' ./out/formula.

Part of the dev-skills plugin — 26 skills, 1 command shipped together

Good fit It is for rendering formulas, equations, and mathematical notation as images.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/LFTPadilla/agent-dev-kit
agentmods
npx agentmods add skills/lftpadilla/agent-dev-kit/tex-render

Made for: Claude Code.

Or install dev-skills, the plugin that ships this one along with the rest of its 26 skills, 1 command.

Wrote 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.

agentmods badge for tex-render

README.md
[![agentmods](https://agentmods.dev/badge/skills/lftpadilla/agent-dev-kit/tex-render/github.svg)](https://agentmods.dev/skills/lftpadilla/agent-dev-kit/tex-render)
Your own site
<a href="https://agentmods.dev/skills/lftpadilla/agent-dev-kit/tex-render"><img src="https://agentmods.dev/badge/skills/lftpadilla/agent-dev-kit/tex-render/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.

agentmods 80×15 button for tex-render

Your own site · 80×15
<a href="https://agentmods.dev/skills/lftpadilla/agent-dev-kit/tex-render"><img src="https://agentmods.dev/badge/skills/lftpadilla/agent-dev-kit/tex-render.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,440 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00063 $0.01440
Opus 5.5 $0.00025 $0.00576
Sonnet 5.5 $0.00013 $0.00288
Haiku 4.5 $0.00006 $0.00144

Measured 1mo ago against content hash 7d912a69d0b9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

tex-render 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 1mo ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/render.js, scripts/validate.js), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

plugins/dev-skills/skills/tex-render/SKILL.md · 126 lines

How it starts

The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.

TeX Render 📐

Renders LaTeX math to PNG, JPEG, WebP, or AVIF (and SVG). Use when you need a viewable image from LaTeX instead of raw code.

Location

The render script lives in the same skill folder as this SKILL.md:

<skill_folder>/
├── SKILL.md
├── package.json
└── scripts/
    └── render.js

Use the directory containing this SKILL.md as the skill path. The script is at scripts/render.js relative to that folder. Invoke: node <skill_folder>/scripts/render.js. The agent loading this skill has the skill path—use it to run the script.

Install

One-time setup. After npm install run npm install` in the skill folder:

cd <skill_folder>
npm install

When to Use

  • User or task asks to "render this equation as image" or "show formula as picture"
  • Your reply would contain LaTeX — render formulas as images first, then respond with plain text

Workflow: Response Contains LaTeX

Output your reply interleaved: whenever you would output LaTeX, do this instead:

  1. Send the preceding plain text — call message with the text written so far (no LaTeX).
  2. Render the LaTeX expression with this skill (default PNG; no --output dataurl). Parse the JSON for the PNG path.
  3. Send the image — call message with action: "send", path set to the rendered PNG, and message as short caption.
  4. Continue outputting the rest of the message. Repeat the cycle (text → render → send image) for each LaTeX block.

Do not output raw LaTeX. Do not ask the user for permission to render — render and send images immediately when LaTeX would appear in your reply. Do not accumulate everything and send at the end — send text and images in order as you go.

Critical: Output in order: plain text → send → LaTeX → render → send image → plain text → send → LaTeX → render → send image → … The user must receive text and images in the natural reading order.

Example: Explaining Lagrangian:
→ Send "The Lagrangian is defined as " → Render L = T - V → Send image with caption "L = T - V" → Send ". The Euler-Lagrange equation is " → Render d/dt(∂L/∂q̇) - ∂L/∂q = 0 → Send image → Send " — this yields the equations of motion."

Read the full file on GitHub · 126 lines

Files

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.

Changes

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.

  1. 1mo ago First seen · 126 lines · 63 tokens per session scan A 7d912a69d0b9

Subscribe to this mod's changes

tex-render is a skill published in the GitHub repository LFTPadilla/agent-dev-kit (2 stars, last pushed 16d ago), licensed MIT. It adds 63 tokens to every session and 1,440 once invoked, about $0.0003 per session on Opus 5.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-31.

Related

Other skills, from other repositories

hypotheses

Turns a research direction into testable hypotheses with predictions, competing explanations and the experiments that discriminate between them, including the design (controls, randomization, blocking), sample size or seed count, the pre-specified analysis, and the result that would falsify each hypothesis. Use when a…

synthetic-sciences/openscience · 99 tokens

omnisci

Run OmniScientist end to end in the OmniScientist CLI using DeepSeek V4 Flash. Turn raw research data (images, signals, audio, video, 3-D, tables, or graphs) and an open direction into perceived evidence, a falsifiable hypothesis, recorded analysis, real citations, a gated candidate paper, PDF, and Overleaf bundle.…

Omni-Scientist/OmniScientist · 145 tokens

coding-standards

Applies language-neutral engineering standards when writing or reviewing code, especially around boundaries, failures, domain models, dependencies, tests, and type safety.

iurysza/android-use · 34 tokens

code-review

Review a code snippet for bugs, security issues, and style, with concrete fixes. Use when the user shares code and asks for feedback or a review.

TeamDzX/myllm-skills · 34 tokens

lean-audit

Whole-repo audit for over-engineering. Like lean-review, but scans the entire codebase instead of a diff: a ranked list of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find bloat"…

utk2103/Prompt-Studio · 98 tokens

lean-review

Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this…

utk2103/Prompt-Studio · 96 tokens