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 skills/dginev/latexml-oxide/resolve-issuenpx skills add dginev/latexml-oxide --skill resolve-issuegit clone --depth 1 https://github.com/dginev/latexml-oxideWrote 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/dginev/latexml-oxide/resolve-issue)<a href="https://agentmods.dev/skills/dginev/latexml-oxide/resolve-issue"><img src="https://agentmods.dev/badge/skills/dginev/latexml-oxide/resolve-issue.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.00129 | $0.03780 |
| Opus 5 | $0.00064 | $0.01890 |
| Sonnet 5 | $0.00026 | $0.00756 |
| Haiku 4.5 | $0.00013 | $0.00378 |
Grade A, and why
resolve-issue 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 5d 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The repo is public; issues now arrive from real users. This skill is the outer
loop that wraps the others (canvas-triage → min-repro → perl-port) into one
issue-to-PR procedure. Faithful translation still governs everything: Perl is
ground truth, never downgrade errors to "pass", diverge only when
OXIDIZED_DESIGN.md sanctions it.
Step 0 — Branch for the ticket (first, always)
One ticket = one branch = one PR. Never work on main, and never pile a new
ticket onto another ticket's branch/PR. Read the issue title to get the number +
a slug, then cut a branch off an up-to-date main:
git switch main && git pull --ff-only
git switch -c fix-<N>-<short-slug> # e.g. fix-293-subimport-standalone
Use a fix- / feat- / docs- prefix per the issue type (Step 1). If triage
(Step 2) later proves the issue is parity / out-of-scope / not-ours, abandon the
branch (git switch main && git branch -D fix-<N>-…) — no PR. Cut the branch off
main even when another ticket's PR is open, so the two stay independent.
Step 1 — Classify the issue
Read the issue in full (gh issue view <N> --json title,body,labels,author).
Pick exactly one type; it selects the path:
| Type | Signal | Path |
|---|---|---|
| 1 — Bug | "X is wrong / crashes / differs from LaTeX" | red/green TDD → patch (the main path below) |
| 2 — Feature | "add / support / it would be nice if" | design plan first → then TDD-implement |
| 3 — Docs | "document / explain / unclear" | refactor the doc with more explanation; verify claims against real behavior |
| 4 — Other | meta, build, question, out-of-scope | triage; usually reduces to 1–3, else answer/ask the user |
Most issues name a TeX source and its conversion → Steps 2–8 apply, PR in Step 9. Types 2/3 add a front-half; see "Type-specific notes".
Step 2 — Reproduce and confirm it's ours
- Put the issue's MWE verbatim into a
.texfile (scratchpad first). Convert with the current binary:cargo run --bin latexml_oxide -- --dest=/tmp/r.html repro.tex. Confirm you see the reported symptom, not something adjacent. - Classify vs Perl before writing any fix (
canvas-triagegolden rules): run same-host Perl verbose, never--quiet, ANSI-strip before grepping. A bug the user reports is only a straight patch when it is GENUINE-RUST-ONLY (Perl behaves correctly, Rust doesn't). If Perl misbehaves identically it is parity/upstream (KNOWN_PERL_ERRORS.md) or asurpass-perldecision — not a silent divergence. If the paper is large, shrink it withmin-reprofirst.
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.
- 5d ago First seen · 235 lines · 129 tokens per session scan A cc811ca171cb
resolve-issue is a skill published in the GitHub repository dginev/latexml-oxide (11 stars, last pushed today), licensed CC0-1.0. It adds 129 tokens to every session and 3,780 once invoked, about $0.0006 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
inclusio
Build, render, lint, and audit LaTeX-first documents (CVs, papers, patents, FAQs, guides) through the Inclusio engine. Use when the user mentions LaTeX, tagged PDFs, PDF/UA-2, PDF/A-4f, WCAG accessibility, the European Accessibility Act (EAA), or asks about building/auditing documents in a repository that has a…
inclusio-publisher
Drive the inclusio publishing engine via MCP — render, audit, and report on PDF/UA-2 tagged documents.
Paper Writing Skills Index
Routing and workflow skill family for paper-writing tasks. Covers manuscript drafting, journal and conference papers, grant proposals, lab reports, group-meeting reports, talks, workshop notes, reviewer rebuttals, academic HTML/PDF/LaTeX output with editable-block contracts, citation grounding, evidence checking, and…
pre-commit-audit
Deliver a fast pre-commit safety scan: file size, anonymity (author / affiliation strings in tex/bib), hardcoded secrets, and invisible-Unicode carriers. Use when the user requests a fast pre-commit safety scan: file size, anonymity (author / affiliation strings in tex/bib), hardcoded secrets, and invisible-Unicode…
latex-diff
Compare two LaTeX files, project directories, or Git revisions and produce human-readable plus machine-readable severity-graded semantic changes. Use when determining what changed between manuscript versions or preparing a revision audit bundle. Not for proofreading one version; use $proofread.
abo-issue-create
Create or reuse GitHub issues for Audiobook Organizer work, then prepare the correct issue branch from master. Use before non-trivial code or documentation edits in this repository.