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/conversiontools/agent-skills/parse-integrationnpx skills add conversiontools/agent-skills --skill parse-integrationgit clone --depth 1 https://github.com/conversiontools/agent-skillsWhat 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.00134 | $0.06486 |
| Opus 5 | $0.00067 | $0.03243 |
| Sonnet 5 | $0.00027 | $0.01297 |
| Haiku 4.5 | $0.00013 | $0.00649 |
Grade A, and why
parse-integration 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST https://api-parse.conversiontools.io/v1/schemas \ How it starts
The opening of the file, as written. The whole thing — 603 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parse: document data extraction
Parse turns documents into structured JSON. You describe the fields you want, send a PDF, scan, or photo, and get those fields back with their values. It handles the layout variation that breaks template-based parsers: the same schema works across suppliers, form revisions, and scan quality.
Two ways to use it, and this skill covers both.
- Run an extraction right now with the
parse_*MCP tools bundled in this plugin. - Build an integration in the user's own codebase against the HTTP API.
The one rule that decides whether an integration works
POST /v1/extract is asynchronous by default. It answers 202 with an extraction id and status: "processing" immediately, and the extracted data is not in that response. You then poll GET /v1/extractions/{id} until status is completed or failed.
Branch on status, never on timing. Every response carries status, so one code path handles all of them. Integrations that assume "if the call took a while, the data must be in there" break the first time a document is slow or fast in the wrong direction, and they break silently.
There are two shortcuts, and both still report status, so the same branch handles them:
wait=Nholds the request open for up to N seconds (max 120) and returns the result inline if it finishes in time. It only applies when the document is uploaded in the same call. If the window expires you get the usual202and id, and you poll.- A cache hit returns
status: "completed"withcached: trueinstantly. The same document with the same field definitions, already extracted on that account, is served from storage and costs no pages.
Using Parse from this agent (MCP tools)
| Tool | What it does |
|---|---|
parse_extract |
Submit a document. Returns an extraction id and status, not the data. |
parse_extraction_status |
Poll one extraction. Returns the data once status is completed. |
parse_list_schemas |
List saved field definitions on the account. |
parse_create_schema |
Create a reusable field definition. |
parse_export |
Turn a completed extraction into CSV or XLSX. |
parse_usage |
Pages used, page limit, remaining, reset date. |
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 · 603 lines · 134 tokens per session scan A 49d33d1e328b
parse-integration is a skill published in the GitHub repository conversiontools/agent-skills (7 stars, last pushed 1mo ago), licensed MIT. It adds 134 tokens to every session and 6,486 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
pr-deslop
Use when cleaning AI slop, verbose commit messages, brittle references, or low-value changes from a branch before review.
changelog
Generate CHANGES entries from branch commits and PR context.
action-worktree
Use when taking one ticket or a related ticket group into its own branch and git worktree for implementation.
agent-messaging-session-relay
Use when sending a message to another Codex/Claude session or telling an agent in another tmux pane a status, finding, instruction, or schema change.
ruff-bump
Use when upgrading Ruff in one repository or a fleet and evaluating newly applicable rules before committing each change.
action-worktrees
Use when fanning several tickets into parallel branches and git worktrees, with related tickets grouped together.