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 skills add run-llama/llamaparse-agent-plugins --skill liteparsegit clone --depth 1 https://github.com/run-llama/llamaparse-agent-pluginsWrote 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/run-llama/llamaparse-agent-plugins/liteparse)<a href="https://agentmods.dev/skills/run-llama/llamaparse-agent-plugins/liteparse"><img src="https://agentmods.dev/badge/skills/run-llama/llamaparse-agent-plugins/liteparse.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.00086 | $0.01518 |
| Opus 5 | $0.00043 | $0.00759 |
| Sonnet 5 | $0.00017 | $0.00304 |
| Haiku 4.5 | $0.00009 | $0.00152 |
Grade A, and why
liteparse 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.
This is a copy
100% identical to liteparse — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Effective LiteParse
Extract text from documents locally with the lit CLI — a fast, model-free parser. This skill is
about using it cheaply: each lit parse re-runs full extraction, and every line you dump into
the conversation is paid for on every subsequent turn. The patterns below come from analyzing real
agent traces where the same PDF was parsed up to 9 times and single image reads cost
140k+ characters of context. Don't repeat those mistakes.
The golden rule: parse ONCE to a file, then search the file
lit parse re-extracts the whole document every time you call it. Re-parsing per search is the #1
waste seen in traces. Parse a document exactly once, to a temp file, then run all your searches
against that file:
# ONE TIME, per document. --no-ocr for born-digital PDFs (almost all reports) — much faster.
lit parse "/abs/path/doc.pdf" --format text --no-ocr -o /tmp/doc.txt && wc -l /tmp/doc.txt
Then search the file with cheap shell tools — never re-run lit parse to search again.
Search discipline — minimize ROUND-TRIPS, then keep results small
Every Bash call is a full model round-trip (latency + re-read of context). The biggest waste after
parsing is a serial loop: grep → look → grep again → sed to read the window → grep again. In
traces this doubled the turn count versus just reading the doc. Two rules fix it:
1. Get context in the SAME command — don't grep then sed. Use grep -C so the surrounding
lines come back with the hit. This removes the follow-up sed turn for the common case:
grep -n -i -C4 "total assets" /tmp/doc.txt | head -40 # location AND its window, one turn
Only fall back to sed -n 'A,Bp' when you already know the exact line and need a wider window
than -C gave you.
2. Batch independent lookups into ONE command. When a question needs several distinct facts (e.g. emissions and revenue), don't spend one turn per term. Probe them together with labels:
for q in "carbon intensity" "scope 1" "total revenue"; do \
echo "=== $q ==="; grep -n -i -C3 "$q" /tmp/doc.txt | head -25; done
What ships with it
1 file 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.
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 · 119 lines · 86 tokens per session scan A c4982f937fe5
liteparse is a skill published in the GitHub repository run-llama/llamaparse-agent-plugins (3 stars, last pushed 24d ago), licensed MIT. It adds 86 tokens to every session and 1,518 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to liteparse, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
skill-doc-delivery
Convert markdown to DOCX, PPTX, XLSX, PDF office documents — use when you need exportable deliverables.
analyze
Analyze a large file (CSV, Excel, PDF, JSON, code) and return a token-efficient summary. Instead of reading thousands of rows or pages, get schema + statistics + sample in under 500 tokens. Use when user mentions a file path, asks to analyze data, pastes many rows, or references a CSV/Excel/PDF/JSON file.
mxl-info
A tool for examining the structure of an MXL tabular document, the 1C format used for printable spreadsheet-like layouts. It shows layout areas, settings, and column sets.
mxl-compile
A tool for compiling a JSON description into an MXL tabular document, the 1C format used for printable spreadsheet-like layouts.
mxl-decompile
A tool for converting an MXL tabular document—the 1C format for printable spreadsheet-like layouts—into a JSON description. JSON is a text format that is easier to read and edit.
opendart-excel
A workflow for creating Excel files from South Korea’s DART company filings, which are public financial reports submitted to the Financial Supervisory Service.