context-parse

A document-conversion tool that turns local files into clean Markdown. It supports PDFs, Office documents, spreadsheets, images, source files, HTML, and other supported formats.

In plain words
What is it for?
Use it to read, summarize, parse, or extract information from an attached local document, with optional page limits for PDFs.
Why use it?
It gives the agent readable text from files that may otherwise be difficult to inspect directly. It can also use OCR, which reads text from scanned pages or images.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/context-dot-dev/cursor-plugin/context-parse
Any agent
npx skills add context-dot-dev/cursor-plugin --skill context-parse
Clone the repo
git clone --depth 1 https://github.com/context-dot-dev/cursor-plugin

Made for: Claude Code, Codex.

Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 217 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00056 $0.00217
Opus 5 $0.00028 $0.00109
Sonnet 5 $0.00011 $0.00043
Haiku 4.5 $0.00006 $0.00022

Measured yesterday against content hash 4e350354d82a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

context-parse 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 yesterday.

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.

skills/context-parse/SKILL.md · 20 lines

What it actually says

Parse documents

Use the Context.dev parse-document MCP tool for local file bytes. Use a scrape tool instead when the source is a web URL.

Workflow

  1. Read the target file and base64-encode its bytes into fileBase64.
  2. Supply the file extension when known.
  3. Preserve links when they matter to the requested output.
  4. For PDFs, restrict the page range when the user names specific pages.
  5. Enable OCR only for scanned pages or when image text is required.
  6. Work from the returned Markdown for subsequent summarization or extraction.

The decoded input must not exceed 25 MiB. Do not upload unrelated files, and do not paste file contents into chat when the user only asked for a derived answer.

Changes

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.

  1. yesterday First seen · 20 lines · 56 tokens per session scan A 4e350354d82a

Subscribe to this mod's changes

context-parse is a skill published in the GitHub repository context-dot-dev/cursor-plugin (4 stars, last pushed 14d ago), licensed MIT. It adds 56 tokens to every session and 217 once invoked, about $0.0003 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens