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/fix-parser-gapnpx skills add sunholo-data/ailang-parse --skill fix-parser-gapgit 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.00116 | $0.01580 |
| Opus 5 | $0.00058 | $0.00790 |
| Sonnet 5 | $0.00023 | $0.00316 |
| Haiku 4.5 | $0.00012 | $0.00158 |
Grade A, and why
fix-parser-gap 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 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.
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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Parser Gap
Implements missing ECMA-376 Office parsing features using a TDD red-to-green workflow: write a failing test first, read the spec, implement in AILANG, verify the test goes green, then re-run benchmarks.
Workflow: Red -> Green -> Benchmark
Step 1: Select the Gap
If the user specifies a feature, use that. Otherwise pick the highest-priority unresolved gap from the audit:
# Show current gap scores (0% = complete gap, 100% = fully handled)
uv run benchmarks/office/eval_gaps.py --verbose
Consult resources/reference.md for the priority table and spec page numbers.
Step 2: RED — Write or Update the Failing Test
This step is critical. No implementation without a failing test first.
Two places tests live:
-
benchmarks/office/eval_gaps.py— Gap analysis checks. Each check is a function likecheck_custom_heading_styles(output)that returns a score from 0.0-1.0. If a check doesn't exist for the gap, add one. If it exists but is too lenient, tighten it. -
benchmarks/officedocbench/ground_truth/challenge_*.json— Hand-verified ground truth for challenge files. These files have"verified": truesoannotate.pywon't overwrite them. If the ground truth doesn't reflect the expected correct behavior, fix it.
Also create or verify the challenge test file in data/test_files/challenge/ — these are generated by benchmarks/create_challenge_files.py using python-docx/openpyxl. If the existing challenge file doesn't test the feature well enough, update the generator.
Run the test to confirm it fails (RED):
uv run benchmarks/office/eval_gaps.py --verbose # Check the specific gap shows 0%
Step 3: Read the Spec
Read the relevant ECMA-376 spec section for the feature being implemented:
# Spec PDF is at:
specs/ecma-376/part1/ECMA-376-1-5th-edition-december-2016-Part1.pdf
Use the page numbers from resources/reference.md. Focus on:
- The XML element structure (tag names, attributes, child elements)
- Where the element appears in the ZIP (which XML file)
- How relationships work (if the feature uses
r:idreferences)
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.
- 2d ago First seen · 154 lines · 116 tokens per session scan A 550bc0101067
fix-parser-gap is a skill published in the GitHub repository sunholo-data/ailang-parse (0 stars, last pushed 2d ago), licensed Apache-2.0. It adds 116 tokens to every session and 1,580 once invoked, about $0.0006 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.
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
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.