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 skills/mishahanin/heading-os/docparsenpx skills add mishahanin/heading-os --skill docparsegit clone --depth 1 https://github.com/mishahanin/heading-osWrote 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/mishahanin/heading-os/docparse)<a href="https://agentmods.dev/skills/mishahanin/heading-os/docparse"><img src="https://agentmods.dev/badge/skills/mishahanin/heading-os/docparse.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.00135 | $0.01691 |
| Opus 5 | $0.00068 | $0.00846 |
| Sonnet 5 | $0.00027 | $0.00338 |
| Haiku 4.5 | $0.00014 | $0.00169 |
Grade A, and why
docparse 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- docparse — 97% identical, 14 lines differ
How it starts
The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DocParse - Document Parsing with Visual Citations
Parse documents and answer questions with spatially-grounded visual citations. Every cited fact is traced to an exact location on the source page.
Variables
$ARGUMENTS- file path(s) or directory, optional question in quotes- Examples:
/docparse datastore/corporate/presentations/deck.pdf/docparse datastore/books/ "What are the key principles?"/docparse report.pdf --report
Phase 0 - Setup & Context
-
Run prerequisite check:
python scripts/docparse.py setup --checkIf any check fails, print the install instructions and STOP.
-
Parse
$ARGUMENTS:- Extract file path(s) or directory
- Extract optional question (quoted string)
- Check for
--reportflag or if user explicitly asks for "visual citations" / "visual report" - Check for
--pagesspecification (e.g.,--pages 1-10)
-
If a directory was given, discover supported files:
# Use Glob to find PDFs, DOCX, PPTX, XLSX in the directory -
For documents over 50 pages, ask the user which page range to parse. Never parse 100+ pages without an explicit
--pagesrestriction.
Phase 1 - Parse
Run the parser:
python scripts/docparse.py parse \
--files "<file1>" "<file2>" \
[--pages "1-10"] \
[--dpi 150] \
--output-json /tmp/docparse_parsed.json
Read the output JSON and present a summary:
- Number of files and pages parsed
- Cache hits vs fresh parses
- Total text items extracted
Phase 2 - Analysis
If the user asked a question:
-
Read
/tmp/docparse_parsed.jsonfocusing on each page'stextfield. Do NOT read rawtext_itemsarrays - those are for the bounding box engine only. -
Analyze the text to answer the question. Identify specific passages that support the answer.
-
For each cited passage, extract an exact verbatim quote from the parsed text:
- Character-for-character exact (this is critical for bounding box lookup)
- Prefer short quotes under 60 characters
- Quote evidence (numbers, data values, key phrases), not just labels
- Include 5-15 citations per answer
What ships with it
2 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.
- 3d ago First seen · 200 lines · 135 tokens per session scan A 6e598c7f6b0d
docparse is a skill published in the GitHub repository mishahanin/heading-os (11 stars, last pushed 4d ago), licensed Apache-2.0. It adds 135 tokens to every session and 1,691 once invoked, about $0.0007 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 skills, from other repositories
markdown-converter
Markdown conversion: PDF, Office, HTML, data, OCR, audio, ZIP, YouTube.
superlinked-docs
Offload document, image, and structured-output work to the Superlinked inference cluster: convert PDF/DOCX/PPTX/XLSX/HTML/scans to clean markdown, describe an image (caption + tags), or produce schema/grammar-constrained JSON off the cluster — instead of ingesting the file directly, which can reduce the tokens billed…
liteparse
Parse documents into LLM-ready content entirely on the local machine — PDF / DOCX / XLSX / PPTX / images → Markdown, structured JSON (with bounding boxes), or page screenshots, via the lit CLI. No cloud, no LLM, works offline. Use whenever the user attaches or points to a document that must be read before reasoning…
office-artifacts
Generate real DOCX, PPTX, XLSX, PDF, CSV files using python-docx / python-pptx / openpyxl / reportlab by writing them into the dispatch artifacts dir, then explicitly deliver each one with cloud deliver . Use whenever the user asks for documents, slides, spreadsheets, reports, or PDFs.
cli-anything-wps
WPS Office CLI — JSON数据驱动PPT自动生成 + 命令行操控WPS文字/表格/演示文稿.
feishu-cli-docs
飞书文档统一入口,覆盖读取和分析 docx/wiki/sheet、创建与编辑文档、Markdown 导入、 docx/wiki/sheet 导出 Markdown/PDF/Word/Excel,以及云盘原生 .md 文件 CRUD。用户要求阅读、 总结、创建、追加、覆盖、替换或删除文档内容,把 Markdown 导入飞书并转换 Mermaid/PlantUML/SVG、 下载图片或导出本地文件、 比较、覆盖或查找替换原生 Markdown 时必须使用本 Skill。 本 Skill 只处理正文内容和文档/Markdown 文件转换。明确禁止用于文档评论、二进制文件导入、 云盘目录和权限管理,这些使用…