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/sunholo-data/ailang-parse/verify-docsnpx skills add sunholo-data/ailang-parse --skill verify-docsgit clone --depth 1 https://github.com/sunholo-data/ailang-parseWhat 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.00920 |
| Opus 5 | $0.00068 | $0.00460 |
| Sonnet 5 | $0.00027 | $0.00184 |
| Haiku 4.5 | $0.00014 | $0.00092 |
Grade A, and why
verify-docs 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify Generated Documents
Run the document generation verification loop to check that generated Office files are structurally valid, open in Python libraries, and roundtrip through AILANG Parse correctly.
What This Does
Three levels of verification on all files in data/examples/:
- L1 Structure — ZIP well-formedness, required entries present, XML validity
- L2 Library — python-docx, python-pptx, openpyxl open without errors, AND
the DOCX table grid is inspected: every row must span exactly the columns
w:tblGriddeclares, and every cell must be iterable - L2b Parts — DOCX package wiring (declared, related, present)
- L4 Roundtrip — Parse through AILANG Parse, verify blocks are preserved
Opening a file is not verifying it. LibreOffice tolerates malformed table geometry that python-docx rejects and Word offers to repair, so invalid output shipped twice while every check was green. Anything generated must have its structure read back, which is what the L2 grid assertion does.
Usage
Run the verification script:
uv run --with python-pptx --with openpyxl --with python-docx benchmarks/verify_generated.py
Also run the round-trip suite
verify_generated.py only covers data/examples/. After any parser or
generator change also run:
uv run benchmarks/roundtrip_check.py # parse -> markdown -> parse, 101 files
It asserts table dimensions, cell text, grid width and heading sequence survive a trip through markdown — the writer the office suite cannot see, because every golden is JSON.
Building a test document
The cheapest way to exercise the generators is to write markdown and convert it: front matter, inline formatting, links, images, fenced code, blockquotes, nested lists and aligned/spanned tables all round-trip. Headers, footers, comments and tracked changes are not expressible in markdown — convert an existing document that has them instead.
With Regeneration
If generator code has changed, regenerate demo files first, then verify:
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.
- yesterday First seen · 91 lines · 135 tokens per session scan A eb3587e3ae28
verify-docs is a skill published in the GitHub repository sunholo-data/ailang-parse (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 135 tokens to every session and 920 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-31.
Other skills, from other repositories
document-converter
Convert Office documents (PPTX, DOCX, XLSX, PDF, HTML, CSV, JSON, XML, images) to Markdown using Microsoft MarkItDown. Provides the agent with conversion strategies for academic and research workflows.
office-router
Route Office requests into the correct xlsx, docx, or pptx workflow, while preferring Slidev for new presentation drafts unless .pptx is explicitly required.
doc-converter
Universal document format converter - DOCX, PDF, Markdown, HTML, TXT.
document-processing
End-to-end document processing agent skill covering PDF manipulation (extract, merge, split, rotate, watermark, form-fill, OCR), DOCX creation and editing (templates, mail-merge, style management), XLSX spreadsheet handling (formulas, charts, pivot tables, data analysis), PPTX presentation generation (layouts, charts…
docx-architecture-audit
Audit the office-open-xml-viewer DOCX layout architecture for a single immutable layout-to-paint pipeline. Use after major DOCX layout, pagination, measurement, paint, parser-model, worker, or compatibility changes, and before declaring Issue.
office-artifacts
Use when creating, opening, reading, or editing Office artifacts such as LibreOffice-native ODT/ODS/ODP files and compatibility DOCX/XLSX/PPTX files with the officeartifact tool.