Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add mishahanin/heading-os-marketplace/plugin install heading-intelWrote 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-marketplace/docparse)<a href="https://agentmods.dev/skills/mishahanin/heading-os-marketplace/docparse"><img src="https://agentmods.dev/badge/skills/mishahanin/heading-os-marketplace/docparse/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mishahanin/heading-os-marketplace/docparse"><img src="https://agentmods.dev/badge/skills/mishahanin/heading-os-marketplace/docparse.svg" alt="Reviewed on agentmods" width="80" 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.00135 | $0.01758 |
| Opus 5 | $0.00068 | $0.00879 |
| Sonnet 5 | $0.00027 | $0.00352 |
| Haiku 4.5 | $0.00014 | $0.00176 |
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 10d 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
97% identical to docparse — 8 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 — 204 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 "${CLAUDE_PLUGIN_ROOT}"/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 "${CLAUDE_PLUGIN_ROOT}"/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.
- 10d ago First seen · 204 lines · 135 tokens per session scan A cb32c5f7c07f
docparse is a skill published in the GitHub repository mishahanin/heading-os-marketplace (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 135 tokens to every session and 1,758 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to docparse, differing in 8 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.
doc-reader
A document parser for Korean government, court, and business files, including HWP, HWPX, PDF, XLSX, and DOCX. It converts them to Markdown while extracting tables, form fields, metadata, and document differences.
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.
recipe-bulk-download-folder
List and download all files from a Google Drive folder.
sap-docs-extract
Reads a SAP design document (Excel .xlsx, Word .docx, PDF) — or an existing work folder / a raw.txt file — and extracts structured information into separate text files by type: program summary, domains, data elements, tables, error messages, text elements, and process logic. From a document it creates a fresh work…
faostat-analytical-brief
Use when the user wants a short, FAOSTAT-style analytical brief — a multi-page PDF policy document in the FAOSTAT house visual style, with a HIGHLIGHTS box, global/regional/country sections, numbered figures with source lines, explanatory notes, and a data appendix. Use when the user asks for "an analytical brief on…