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 llamaparsegit 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/llamaparse)<a href="https://agentmods.dev/skills/run-llama/llamaparse-agent-plugins/llamaparse"><img src="https://agentmods.dev/badge/skills/run-llama/llamaparse-agent-plugins/llamaparse.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.00030 | $0.01639 |
| Opus 5 | $0.00015 | $0.00820 |
| Sonnet 5 | $0.00006 | $0.00328 |
| Haiku 4.5 | $0.00003 | $0.00164 |
Grade A, and why
llamaparse scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const response = await fetch(image.presigned_url, { This is a copy
100% identical to llamaparse — 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LlamaParse Skill
Parse unstructured documents (such as PDF, DOCX, PPTX, XLSX) with LlamaParse and extract their contents (text, markdown, images...).
Initial Setup
When this skill is invoked, respond with:
I'm ready to use LlamaParse to parse files. Before we begin, please confirm that:
- `LLAMA_CLOUD_API_KEY` is set as environment variable within the current environment
- `@llamaindex/llama-cloud@latest` is installed and available within the current Node environment
If both of them are set, please provide:
1. One or more files to be parsed
2. Specific parsing options, such as tier, API version, custom prompt, processing options...
3. Any requests you might have regarding the parsed content of the file.
I will produce a Typescript script to run the parsing job and, once you approved its execution, I will report the results back to you based on your request.
Then wait for the user's input.
Step 0 — Install llama-cloud (optional)
If the user does not have the @llamaindex/llama-cloud package installed, add it to the current environment by running:
npm install @llamaindex/llama-cloud@latest
Step 1 — Produce a Typescript Script
Once the user confirms the environment variables are set and provides the necessary details for the parsing job, produce a typescript script.
As a source of truth for the TS script, you can:
- Refer to the example.ts script, which covers most of the necessary configurations for LlamaParse
- Refer to the complete LlamaParse Documentation, fetching the
https://developers.llamaindex.ai/python/cloud/llamaparse/api-v2-guide/page.
Scripting Best Practices
Follow these guidelines when generating scripts:
1. Always Use the Top-Level LlamaCloud Client
Use LlamaCloud (the API client) for all parsing operations:
import LlamaCloud from "@llamaindex/llama-cloud";
// Define a client
const client = new LlamaCloud({
apiKey: process.env["LLAMA_CLOUD_API_KEY"], // This is the default and can be omitted
});
What ships with it
3 files 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.
- 7d ago First seen · 221 lines · 30 tokens per session scan A c0f9d5a8b6e1
llamaparse is a skill published in the GitHub repository run-llama/llamaparse-agent-plugins (3 stars, last pushed 24d ago), licensed MIT. It adds 30 tokens to every session and 1,639 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to llamaparse, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
yonsei-certificate-assistant
A cross-platform helper for Yonsei’s electronic certificate service, including its authenticated ReportX ticket and free online-print route. It can decode the ticket and render a PDF, or diagnose native Windows ReportX when physical printing is specifically requested.
render-reportx-fp3-pdf
Render a decoded ReportX/FastReport VCL prepared-report FP3 XML stream into a local PDF on Windows, macOS, or Linux without native ReportX, a browser, or a physical printer. Use when a Yonsei icert ReportX response has already been decrypted into a primary FP3 component plus image components, when inspecting FP3…
issue-yonsei-certificate
A guide for getting a free Yonsei University certificate as a PDF on Windows, macOS, or Linux. Yonsei is a university in South Korea, and the process uses a virtual PDF printer.
skill-doc-delivery
Convert markdown to DOCX, PPTX, XLSX, PDF office documents — use when you need exportable deliverables.
add-pdf-report
Internal implementation skill invoked by /add-native for app-generated PDF report workflows using expo-print and, when present, expo-sharing.
add-pdf-viewer
Internal implementation skill invoked by /add-native for native PDF control workflows. Handles HTTPS and file URI PDF viewing with @microsoft/power-apps-native-pdf-viewer 0.2.9+.