latexml-oxide: Agent for Claude Code

.claude/agents/log-scanner.md

log-scanner is an agent for Claude Code from dginev/latexml-oxide. It costs 0 tokens per session (669 once invoked), scanned A, original, CC0-1.0.

A read-only tool for scanning many latexml-oxide conversion logs and summarizing their errors, statuses, and error classes. A conversion log records what happened while a LaTeX document was processed.

In plain words
What is it for?
Use it to count conversion outcomes, find first errors for papers, group error types, inspect sweep results, and separately flag logs that could not be parsed.
Why use it?
It replaces manual reading of large log collections and avoids missing errors hidden by color codes, binary data, or incomplete logs.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions CLAUDE.md.

This is dginev/latexml-oxide's own configuration. It tells Claude Code how to work on latexml-oxide itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything latexml-oxide configures →

Reuse

Borrowing it

Nothing to install: this file belongs to dginev/latexml-oxide. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/dginev/latexml-oxide/main/.claude/agents/log-scanner.md
Clone the repo
git clone --depth 1 https://github.com/dginev/latexml-oxide

Made for: Claude Code.

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 log-scanner

README.md
[![agentmods](https://agentmods.dev/badge/agents/dginev/latexml-oxide/log-scanner/github.svg)](https://agentmods.dev/agents/dginev/latexml-oxide/log-scanner)
Your own site
<a href="https://agentmods.dev/agents/dginev/latexml-oxide/log-scanner"><img src="https://agentmods.dev/badge/agents/dginev/latexml-oxide/log-scanner/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 log-scanner

Your own site · 80×15
<a href="https://agentmods.dev/agents/dginev/latexml-oxide/log-scanner"><img src="https://agentmods.dev/badge/agents/dginev/latexml-oxide/log-scanner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 669 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.00000 $0.00669
Opus 5.5 $0.00000 $0.00268
Sonnet 5.5 $0.00000 $0.00134
Haiku 4.5 $0.00000 $0.00067

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

Security

Grade A, and why

log-scanner 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 2mo 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.

.claude/agents/log-scanner.md · 45 lines

How it starts

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

You are a read-only scanner for latexml-oxide conversion logs (sweep output directories, .latexml.log files, cortex result zips). You aggregate; you never interpret, fix, or re-run conversions.

Signal-integrity rules (non-negotiable — from CLAUDE.md)

  • ANSI-strip before any grep. Logs from older binaries carry color codes (\x1b[31mError:), and a naive grep -c '^Error:' silently reports 0 on a paper with hundreds of errors. Always sed 's/\x1b\[[0-9;]*m//g' <log> | grep -acE '^(Error|Fatal):' (the -a matters — logs can contain binary).
  • Prefer the ANSI-free canonical signals over grepping stderr: Status:conversion:N (in the status member of a cortex output zip and on stdout; 3 = fatal, 2 = error, lower = OK/warnings), and the on-disk .latexml.log (color-free by construction).
  • Error-class extraction uses grep -oE 'Error:[a-zA-Z_]+:[a-zA-Z_]+' — never [a-z] only; categories can be uppercase/underscore.
  • Fail toward flagging. A log you cannot parse, or a failing paper with no Error: match, goes into a separate "parse-miss" bucket in your output — never dropped, never counted as success. Parse misses usually mean Fatal:, timeout, or OOM.
  • Multi-file papers: gate on cortex's own Processing content line to find the real main file — papers ship decoy \begin{document} stubs.
  • Never judge a test-suite run by grepping for Error: — a fully green cargo test run deliberately prints Error: lines. Test runs are judged by test result: lines and exit code only. The Error-grep heuristic is for conversion logs exclusively.

Conduct

  • Read-only: no writes outside /tmp scratch, no deletes, no conversions, no builds. unzip -p / zcat for reading archive members is fine.
  • Output compact aggregates (TSV or aligned tables): class counts, per-paper first-error rows, status histograms. Never echo raw log content beyond the single matched error line per paper.
  • Your final text is consumed by the caller as data — return the table, not prose.

Read the full file on GitHub · 45 lines

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. 2mo ago First seen · 45 lines · 0 tokens per session scan A 5149e89b78ff

Subscribe to this mod's changes

log-scanner is an agent published in the GitHub repository dginev/latexml-oxide (18 stars, last pushed yesterday), licensed CC0-1.0. It costs nothing until one of its globs matches a file; then it loads 669 tokens. 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.

Related

log-scanner compared with agents from other repositories

log-scanner next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
log-scannerdginev/latexml-oxideAgent18yesterdayCC0-1.0A0Claude Code
fixerflonat/flonat-researchAgent1493d agoMITA183Claude Code
review-obsidian-guidelinesuphy/obsidian-reminderAgent662yesterdayMITA63Claude Code
debuggerTT-Wang/forgeAgent353d agoMITA17Claude Code
debuggerbostonaholic/rpikitAgent204d agoMITA28Claude Code
loom-advisorcosmix/loomAgent655d agoMITA53Claude Code
evolve-retrospectivemickeyyaya/evolve-loopAgent6todayApache-2.0A51Claude Code