docx-editing

docx-editing is a skill for Claude Code, Codex from lawyerllsx-dotcom/Legal-Workflow-Chain. It costs 56 tokens per session (1,983 once invoked), scanned A, a copy of docx-editing, MIT.

A local tool for editing existing Microsoft Word .docx files while preserving formatting and recording changes for review.

In plain words
What is it for?
Use it to edit clauses, add comments or footnotes, adjust layout, compare documents, and produce tracked-change redlines.
Why use it?
It allows precise edits to an already-written document without losing its layout or hiding what changed.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for openclaw. Also seen: built for openclaw.

Good fit Use it to edit clauses, add comments or footnotes, adjust layout, compare documents, and produce tracked-change redlines.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/lawyerllsx-dotcom/legal-workflow-chain/docx-editing
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.

Any agent
npx skills add lawyerllsx-dotcom/Legal-Workflow-Chain --skill docx-editing
Clone the repo
git clone --depth 1 https://github.com/lawyerllsx-dotcom/Legal-Workflow-Chain

Made for: Claude Code, Codex.

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

agentmods badge for docx-editing

README.md
[![agentmods](https://agentmods.dev/badge/skills/lawyerllsx-dotcom/legal-workflow-chain/docx-editing/github.svg)](https://agentmods.dev/skills/lawyerllsx-dotcom/legal-workflow-chain/docx-editing)
Your own site
<a href="https://agentmods.dev/skills/lawyerllsx-dotcom/legal-workflow-chain/docx-editing"><img src="https://agentmods.dev/badge/skills/lawyerllsx-dotcom/legal-workflow-chain/docx-editing/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.

agentmods 80×15 button for docx-editing

Your own site · 80×15
<a href="https://agentmods.dev/skills/lawyerllsx-dotcom/legal-workflow-chain/docx-editing"><img src="https://agentmods.dev/badge/skills/lawyerllsx-dotcom/legal-workflow-chain/docx-editing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,983 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 98% copy Near-identical to another mod 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.1 $0.00056 $0.01983
Opus 5 $0.00028 $0.00992
Sonnet 5 $0.00011 $0.00397
Haiku 4.5 $0.00006 $0.00198

Measured 11d ago against content hash 8b043c556b2c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

docx-editing 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 11d 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.

Origin

This is a copy

98% identical to docx-editing — 11 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/docx-editing/SKILL.md · 178 lines

How it starts

The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Editing .docx Files with Safe-DOCX

Safe-DOCX is a local MCP server for surgically editing existing .docx files. It preserves formatting, generates tracked-changes redlines, and runs entirely on the local filesystem — no hosted endpoint, no data leaves the machine.

Safety Model

  • Local-only stdio runtime — the MCP server runs as a child process, never binds a port.
  • Path policy — only files under ~/ (home directory) and system temp directories are accessible. Symlinks must resolve to allowed roots.
  • Archive guardrails — zip bomb detection and hostile payload rejection protect against malformed .docx inputs.

When to Use This Skill

Use Safe-DOCX when you need to:

  • Change clauses or paragraphs in an existing .docx
  • Insert or delete content with formatting preservation
  • Add comments or footnotes for reviewers
  • Produce a tracked-changes redline from edits
  • Compare two .docx files into a redline
  • Extract revisions to structured JSON
  • Apply layout formatting (spacing, row heights, cell padding)

Not for From-Scratch Generation

Safe-DOCX edits already-existing .docx files — it does not create documents from blank. For new document generation, use a template-filling workflow (e.g. OpenAgreements). Safe-DOCX can refine generated docs downstream.

不触发情况(强制排除)

以下场景即使提到 DOCX/Word,也不触发本 skill:

  • 编程/脚本类:"写个脚本/程序/代码 读取/生成/处理 DOCX"——这是编程任务,不是文档编辑
  • 库/工具推荐类:"用什么库读取 DOCX""python-docx 怎么用"——这是技术问答
  • 格式转换类:"把 DOCX 转成 PDF/Markdown"——这是文件转换任务(除非用户明确说"用 Safe-DOCX")
  • 从零生成:创建全新文档而非编辑已有文件

判定原则:用户目标是写代码/脚本,而非直接编辑文档内容 → 不触发

Quick Start

1. read_file(file_path="~/doc.docx")        → see paragraphs + _bk_* IDs
2. grep(file_path="~/doc.docx", patterns=["target phrase"])  → find paragraph IDs
3. replace_text(session_id, target_paragraph_id, old_string, new_string, instruction)
4. save(session_id, save_to_local_path="~/doc-edited.docx")

Core Workflow: Read, Locate, Edit, Save

Step 1 — Read. Call read_file with format: "toon" (token-efficient table) to see paragraphs and their stable _bk_* IDs.

Read the full file on GitHub · 178 lines

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. 11d ago First seen · 178 lines · 56 tokens per session scan A 8b043c556b2c

Subscribe to this mod's changes

docx-editing is a skill published in the GitHub repository lawyerllsx-dotcom/Legal-Workflow-Chain (5 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 1,983 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to docx-editing, differing in 11 lines, and is treated as a copy.

Related

Other skills, from other repositories