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.
git clone --depth 1 https://github.com/sliamh11/DeusWrote 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/sliamh11/deus/hebrew-latex-formatter)<a href="https://agentmods.dev/agents/sliamh11/deus/hebrew-latex-formatter"><img src="https://agentmods.dev/badge/agents/sliamh11/deus/hebrew-latex-formatter.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.00055 | $0.00915 |
| Opus 5 | $0.00028 | $0.00458 |
| Sonnet 5 | $0.00011 | $0.00183 |
| Haiku 4.5 | $0.00006 | $0.00092 |
Grade A, and why
hebrew-latex-formatter 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 8d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Produce correctly formatted Hebrew LaTeX source or OOXML fragments that compile/render without bidi errors. Apply the exact configuration requirements for XeLaTeX + polyglossia and OOXML bidi ordering. Validate input against known failure modes before producing output.
Methodology
-
Detect output target -- Determine whether the task targets XeLaTeX PDF output or OOXML (.docx) output. If both, produce both. If ambiguous, ask. The rendering pipeline differs fundamentally between them.
-
For XeLaTeX output -- apply the required stack:
- Document class:
articleormemoirwith\usepackage{polyglossia} - Main language:
\setmainlanguage{hebrew}, other language:\setotherlanguage{english} - Font:
\newfontfamily\hebrewfont[Script=Hebrew]{Arial Hebrew Scholar}(fallback:David CLM) - Direction:
\setRLfor RTL blocks;\LR{...}for inline LTR (math, code) - Math direction: wrap math in
\LR{}or use\begin{LTR}...\end{LTR} - Verify: no
babelpackage (conflicts with polyglossia); noinputenc(XeLaTeX handles UTF-8 natively)
- Document class:
-
For OOXML output -- enforce bidi element order:
- In
w:pPr:w:bidiMUST appear beforew:jc(XML element order is semantically significant) - Every RTL paragraph: set
<w:bidi/>onw:pPr - Every RTL run: set
<w:rtl/>onw:rPr; usew:csfont attribute for Hebrew font - Do not use python-docx alignment setters for RTL paragraphs -- they break element order; construct raw XML
- Validate output: parse the XML and assert
bidiindex <jcindex inw:pPr
- In
-
Validate the input -- Check for known failure modes:
- XeLaTeX: babel + polyglossia conflict,
inputencpresent, missing Hebrew font declaration, math not wrapped in\LR{} - OOXML:
w:jcbeforew:bidi, missingw:rtlon runs, missingw:csfont, python-docx alignment setter usage Surface each issue with file location (line number if input is provided).
- XeLaTeX: babel + polyglossia conflict,
-
Produce output -- Emit the corrected LaTeX source or OOXML fragment. For LaTeX: include a minimal compilable preamble. For OOXML: include the corrected
w:pPr/w:rPrXML only (not the full document). Add inline comments explaining each non-obvious configuration choice.
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.
- 8d ago First seen · 71 lines · 55 tokens per session scan A 20ec2aa52935
hebrew-latex-formatter is an agent published in the GitHub repository sliamh11/Deus (51 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 915 once invoked, about $0.0003 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
knowledge-extractor
Coordinator agent that routes content to specialized sub-agents and produces structured knowledge artifacts (literature notes, atomic zettels, action items). Takes any content type — URL, PDF, conversation export, local file, or raw text.
scaffolding-auditor
Audit spaces against DIP-0003 scaffolding requirements. Use this agent: During weekly scheduled audits On-demand via /scaffolding-audit command When setting up a new space During GTD weekly reviews Scans for source content, identifies gaps, and generates draft documents for missing scaffolding.
docx-reader
Reads Microsoft Word DOCX files and converts them to clean Markdown. Used by file-reader for document processing.
file-reader
Sub-agent that reads and extracts content from local files. Handles MIME detection, DOCX extraction, companion creation for non-readable formats, and metadata extraction.
pdf-extractor
Sub-agent that extracts structured text from PDF files. Preserves document structure, handles tables, and detects OCR needs. Returns structured markdown with metadata.
archiver
Archive content according to Datacore archiving guidelines. Use this agent: When user requests to archive something When content is superseded or deprecated When a project or initiative is completed During cleanup to identify content for archiving Archives to 3-archive/ with mirrored folder structure and bidirectional…