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 skills add holon-run/holon --skill docxgit clone --depth 1 https://github.com/holon-run/holonWrote 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/holon-run/holon/docx)<a href="https://agentmods.dev/skills/holon-run/holon/docx"><img src="https://agentmods.dev/badge/skills/holon-run/holon/docx/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/holon-run/holon/docx"><img src="https://agentmods.dev/badge/skills/holon-run/holon/docx.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.00032 | $0.00807 |
| Opus 5.5 | $0.00013 | $0.00323 |
| Sonnet 5.5 | $0.00006 | $0.00161 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
docx 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 1mo 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DOCX
Summary
Use this skill for .docx reports, memos, letters, meeting notes, proposals,
and other word-processing documents. Prefer python-docx for common document
structures and use an available local LibreOffice renderer for pagination and
visual review.
This skill does not imply complete support for every Word or OOXML feature.
When To Use
- Creating a structured document from notes, Markdown, or source material
- Inspecting paragraphs, headings, tables, images, styles, and metadata
- Making bounded edits to a conventional DOCX
- Converting a DOCX to PDF for review
- Checking document structure, pagination, and consistency
Safety Boundaries
- Preserve the source and write a new
.docxby default. - Treat macros, links, fields, embedded files, OLE objects, comments, revisions, and custom XML as untrusted input.
- Never execute macros, update external fields, open embedded objects, or follow document links automatically.
- Ask before resolving external assets or uploading content.
- Do not claim lossless editing for content controls, complex fields, tracked changes, equations, signatures, embedded objects, or package parts not modeled by the selected library.
Use read-only analysis or create a new document when preserving unsupported features is material to the request.
Backend Selection
- Use python-docx for common paragraphs, styles, lists, sections, tables, headers, footers, and images.
- Use LibreOffice headless only when installed and approved as a local renderer or converter. Record the actual backend.
- Use package-level XML inspection for risk inventory or verification, not as a default editing strategy.
Do not silently install Python packages, fonts, LibreOffice, or converters.
Workflow
- Confirm the document type, audience, language, page or word target, style guide, template, citations, output path, and whether comments or revisions must be preserved.
- Inspect an existing package before editing. Record styles, sections, headers and footers, tables, fields, links, comments, revisions, macros, signatures, embedded objects, and unknown parts.
- Plan the heading hierarchy, sections, tables, figures, references, and page furniture before generation.
- Select a backend and restrict changes to features it represents reliably.
- Write a new output file. Avoid raw OOXML edits unless the relationship and namespace effects are fully understood.
- Reopen the result and verify expected headings, paragraph and table counts, relationships, images, sections, headers, and footers.
- Render to PDF or pages when possible. Inspect page breaks, widows and orphans, clipped tables, heading placement, list numbering, headers, footers, and font substitution.
- Sample-check important facts, citations, figures, and tables against source material.
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.
- 1mo ago First seen · 88 lines · 32 tokens per session scan A 5a6ffd4be1fe
docx is a skill published in the GitHub repository holon-run/holon (166 stars, last pushed yesterday), licensed Apache-2.0. It adds 32 tokens to every session and 807 once invoked, about $0.0001 per session on Opus 5.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-09-07.
Other skills, from other repositories
google-sheets
Google Sheets via gws: read/write cells, append rows, structured batch edits.
google-docs
Google Docs via gws: read, append text, structured batch edits.
docx
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', '.docx', or requests to produce professional documents with headings, tables of contents, page numbers, or letterheads. Also use for extracting content from .docx…
data-analysis
Use this skill when the user asks to analyze data from CSV, JSON, Excel, or database exports — including exploring datasets, computing statistics, creating visualizations, finding patterns, cleaning data, or building dashboards. Trigger whenever the user provides a data file and wants insights, charts, or…
Use this skill whenever the user wants to do anything with PDF files — reading, extracting text or tables, merging, splitting, rotating, creating new PDFs, adding watermarks, OCR on scanned documents, encrypting/decrypting, or filling forms. Trigger whenever a .pdf file is mentioned or needs to be produced.
pptx
Use this skill any time a .pptx file is involved — creating slide decks, reading or extracting content from presentations, editing existing slides, or converting between formats. Trigger whenever the user mentions 'deck', 'slides', 'presentation', or references a .pptx filename.