docx

A toolset for creating, editing, repairing, and reviewing Microsoft Word documents in .docx format. It covers document generation, simple edits, comments, tracked changes, conversion from Markdown, and validation.

In plain words
What is it for?
Use it to create reports, edit existing Word files, add comments or tracked changes, convert multi-section Markdown to Word, and validate or repair .docx files.
Why use it?
It gives coding agents defined workflows for common Word-document tasks and checks that document files are valid. It also provides a fallback output location when a requested directory cannot be used.

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/xyruscode/ai-sync/docx
Any agent
npx skills add XyrusCode/ai-sync --skill docx
Clone the repo
git clone --depth 1 https://github.com/XyrusCode/ai-sync

Made for: Claude Code, Codex.

Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,080 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.00050 $0.02080
Opus 5 $0.00025 $0.01040
Sonnet 5 $0.00010 $0.00416
Haiku 4.5 $0.00005 $0.00208

Measured yesterday against content hash aa8600d580d5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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

The scan reads SKILL.md. This mod also ships 15 executable files (assets/example.js, scripts/__init__.py, scripts/docx_lib/__init__.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.

skills/docx/SKILL.md · 145 lines

How it starts

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

DOCX Skill

Route

Task Route Read
Create a new .docx docx-js script, then {skill_path}/scripts/docx build references/docx-js.md, then assets/example.js
Create native Word equations docx-js plus literal OMML helpers references/docx-js.md, references/omml.md
Edit text/style in an existing .docx python-docx for simple in-place edits references/editing.md
Add comments or tracked changes DocxContext editing module references/editing.md
Convert swarm-assembled Markdown to .docx {skill_path}/scripts/docx md2docx <file.md> references/md2docx-reference.md
Validate or repair a .docx {skill_path}/scripts/docx validate <file.docx> this file

Output path: write to the path the user requested. If its directory is not writable (e.g. a container path like /mnt/... that does not exist here), fall back to ./outputs/ under the current working directory, create it, and report the final path. Never fail just because a hardcoded absolute directory is missing.

When to use md2docx (gate): only for a multi-section Markdown report assembled by a swarm writing skill — i.e. there is a *.agent.final.md or several *_sec{NN}.md files produced by sub-agents, with standard Markdown footnotes ([^id] + [^id]: Title. Date. URL) for citations. For a one-off document the user asks you to write, author it natively with docx-js (the Create route); hand-authored layout is cleaner than converted Markdown.

Skill Map

docx/
├── SKILL.md                 # routing, required commands, validation contract
├── references/
│   ├── docx-js.md           # creation standard: JS skeleton, TOC, visual defaults, few-shots
│   ├── editing.md           # existing-document edits, comments, tracked changes
│   ├── omml.md              # native Word equation patterns and ordering traps
│   └── md2docx-reference.md # swarm Markdown → docx citation pipeline
├── assets/
│   └── example.js           # small build-tested docx-js seed
└── scripts/
    ├── docx                 # only entry point to call
    ├── setup_node_env       # detect Node docx dependency; optional explicit cache install
    ├── lint_docx_js.py      # static checks for docx-js authoring mistakes
    ├── validate_all.py      # repair + validation pipeline
    ├── md2docx/             # Markdown (standard footnotes) → docx citation pipeline
    └── docx_lib/            # OOXML/OPC checks and editing helpers

Read the full file on GitHub · 145 lines

Files

What ships with it

60 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. yesterday First seen · 145 lines · 50 tokens per session scan A aa8600d580d5

Subscribe to this mod's changes

docx is a skill published in the GitHub repository XyrusCode/ai-sync (2 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 2,080 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens