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 lfyxhappy/lfcode --skill pdf-processorgit clone --depth 1 https://github.com/lfyxhappy/lfcodeWrote 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/lfyxhappy/lfcode/pdf-processor)<a href="https://agentmods.dev/skills/lfyxhappy/lfcode/pdf-processor"><img src="https://agentmods.dev/badge/skills/lfyxhappy/lfcode/pdf-processor.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.00082 | $0.00363 |
| Opus 5 | $0.00041 | $0.00181 |
| Sonnet 5 | $0.00016 | $0.00073 |
| Haiku 4.5 | $0.00008 | $0.00036 |
Grade A, and why
pdf-processor 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 2d 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.
What it actually says
PDF Processor
Handle PDFs as potentially lossy, layout-sensitive artifacts.
Workflow
- Inspect file existence, page count, metadata, encryption, text layer, images, forms, annotations, and expected output without exposing sensitive content.
- Check which local command, library, renderer, or OCR runtime is actually available. Choose the least lossy path for the requested operation.
- Work on a copy or produce a new output. Keep page order, orientation, links, fonts, accessibility tags, and annotations when the format and tool support them.
- For OCR or extraction, preserve page references and mark low-confidence or image-only text. For redaction, verify that underlying text and metadata are not still recoverable.
- Validate output existence, openability, page count, dimensions, text or image presence, and representative rendered pages. Check edge cases such as blank, rotated, scanned, and large pages.
Boundaries
- Never claim a redaction is secure without checking the actual PDF content layers and metadata.
- Do not upload PDFs to external services, overwrite the source, or fabricate missing text without explicit authorization.
- Do not treat a successful command exit as proof of visual or semantic correctness.
Completion check
Report the input and output paths, operation, tools actually used, structural and render checks, OCR uncertainty, and any unsupported feature.
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.
- 2d ago First seen · 27 lines · 82 tokens per session scan A 70ac7cf37e06
pdf-processor is a skill published in the GitHub repository lfyxhappy/lfcode (2 stars, last pushed 4d ago), licensed MIT. It adds 82 tokens to every session and 363 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-09-05.
Other skills, from other repositories
Read, create, inspect, render, and verify PDF files where visual layout matters, including fillable AcroForms. Use Poppler rendering plus Python tools such as reportlab, pdfplumber, and pypdf for generation and extraction.
Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.
Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.
Read, extract, split, merge, rotate, watermark, fill, OCR, or create PDF files with verification of page counts and text extraction.
liteparse
Use this skill when the user asks to parse, perform multi-format document conversion or spatially extract text from an unstructured file (PDF, DOCX, PPTX, XLSX, images, etc.) locally without cloud dependencies.
treatment-plans
Generate concise (3-4 page), focused medical treatment plans in LaTeX/PDF format for all clinical specialties. Supports general medical treatment, rehabilitation therapy, mental health care, chronic disease management, perioperative care, and pain management. Includes SMART goal frameworks, evidence-based…