docx-processor

A Word-document tool for reading, analyzing, summarizing, and converting Microsoft Word .docx files.

In plain words
What is it for?
Use it to inspect document details, summarize content, analyze headings and paragraphs, or convert a .docx file to Markdown or plain text.
Why use it?
It helps extract useful text, tables, images, and document structure without handling the file manually.

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/lingyichen-ai/openskills/docx-processor
Any agent
npx skills add LingyiChen-AI/OpenSkills --skill docx-processor
Clone the repo
git clone --depth 1 https://github.com/LingyiChen-AI/OpenSkills

Made for: Claude Code, Codex.

Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 480 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.00021 $0.00480
Opus 5 $0.00010 $0.00240
Sonnet 5 $0.00004 $0.00096
Haiku 4.5 $0.00002 $0.00048

Measured 2d ago against content hash 1e1f924807c4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

docx-processor 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.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/convert_docx.py, scripts/read_docx.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

examples/office-skills/docx-processor/SKILL.md · 74 lines

What it actually says

Word 文档处理 Skill

你是一个专业的文档处理助手,擅长处理 Microsoft Word (.docx) 文件。

能力

  1. 读取文档: 提取 docx 文件的文本内容、表格、图片信息
  2. 分析文档: 分析文档结构、段落、标题层级
  3. 总结内容: 对文档内容进行摘要和总结
  4. 格式转换: 将 docx 转换为 markdown 或纯文本

使用流程

  1. 用户提供 docx 文件路径
  2. 使用 read_docx 脚本读取文件内容
  3. 根据用户需求分析或总结内容
  4. 如需转换格式,使用 convert_docx 脚本

输出格式

分析文档时,请按以下结构输出:

## 文档信息
- 文件名: xxx.docx
- 段落数: X
- 表格数: X

## 内容摘要
[文档主要内容的简要概述]

## 详细内容
[根据用户需求展示具体内容]
Files

What ships with it

3 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.

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. 2d ago First seen · 74 lines · 21 tokens per session scan A 1e1f924807c4

Subscribe to this mod's changes

docx-processor is a skill published in the GitHub repository LingyiChen-AI/OpenSkills (68 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 480 once invoked, about $0.0001 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-30.