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 agents/dginev/latexml-oxide/log-scannergit 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/agents/dginev/latexml-oxide/log-scanner)<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="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 | $0.00080 | $0.00669 |
| Opus 5 | $0.00040 | $0.00334 |
| Sonnet 5 | $0.00016 | $0.00134 |
| Haiku 4.5 | $0.00008 | $0.00067 |
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 3d 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 — 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 naivegrep -c '^Error:'silently reports 0 on a paper with hundreds of errors. Alwayssed 's/\x1b\[[0-9;]*m//g' <log> | grep -acE '^(Error|Fatal):'(the-amatters — logs can contain binary). - Prefer the ANSI-free canonical signals over grepping stderr:
Status:conversion:N(in thestatusmember 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 meanFatal:, timeout, or OOM. - Multi-file papers: gate on cortex's own
Processing contentline to find the real main file — papers ship decoy\begin{document}stubs. - Never judge a test-suite run by grepping for
Error:— a fully greencargo testrun deliberately printsError:lines. Test runs are judged bytest 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/zcatfor 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.
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.
- 3d ago First seen · 45 lines · 0 tokens per session scan A 5149e89b78ff
log-scanner is an agent published in the GitHub repository dginev/latexml-oxide (11 stars, last pushed 10d ago), licensed CC0-1.0. It adds 80 tokens to every session and 669 once invoked, about $0.0004 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 agents, from other repositories
claim-verify
Verify that cited claims in a paper accurately represent what the source papers actually say. Checks every factual claim against its reference. Read-only with respect to project files (paper, bib, cited PDFs); writes its own Claim Verify Report and typed citation-integrity component at reviews/ /claim-verify/ ..…
peer-reviewer
Use this agent when you need to review someone else's paper — as a peer reviewer, discussant, or for reading group preparation. This agent reads the PDF carefully using split-pdf methodology, spawns parallel sub-agents for citation validation, novelty assessment, and methodology review, scans for hidden prompt…
code-review
Multi-persona orchestrator for adversarial review of R, Python, Julia, or Stata research scripts. Runs an 11-category baseline checklist, then dispatches 3-6 specialist sub-agents (correctness, reproducibility, design, plus optional domain / performance / security) in parallel. Deduplicates findings across reviewers…
fatal-error-check
Fast pre-review check for fatal errors in LaTeX papers. Launch BEFORE full review agents (paper-critic, domain-reviewer, referee2-reviewer). Binary PASS/FAIL verdict in 15-30 seconds. Checks compilation, placeholders, broken references, number contradictions, and section completeness. Examples: Example 1: user: "Quick…
redaccion-claude
Eres un experto en redacción académica en LaTeX para Trabajos de Fin de Grado (TFG) y Máster (TFM) de la Escuela Politécnica Superior (EPS) de la Universidad de Alicante (UA). Versión de plantilla: 2.2.2 (2026).
redaccion
Eres un experto en redacción académica en LaTeX para Trabajos de Fin de Grado (TFG) y Máster (TFM) de la Escuela Politécnica Superior (EPS) de la Universidad de Alicante (UA).