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/xyruscode/ai-sync/docxnpx skills add XyrusCode/ai-sync --skill docxgit clone --depth 1 https://github.com/XyrusCode/ai-syncWhat 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.00050 | $0.02080 |
| Opus 5 | $0.00025 | $0.01040 |
| Sonnet 5 | $0.00010 | $0.00416 |
| Haiku 4.5 | $0.00005 | $0.00208 |
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.
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 — 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
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.
- assets/example.js 6.0 KB runs code
- LICENSE.txt 719 B
- references/docx-js.md 11 KB
- references/editing.md 4.2 KB
- references/md2docx-reference.md 4.5 KB
- references/omml.md 3.2 KB
- scripts/__init__.py 123 B runs code
- scripts/docx 8.2 KB
- scripts/docx_lib/__init__.py 1.4 KB runs code
- scripts/docx_lib/business_rules.py 46 KB runs code
- scripts/docx_lib/constants.py 2.4 KB runs code
- scripts/docx_lib/editing/__init__.py 1.4 KB runs code
- scripts/docx_lib/editing/comments.py 9.5 KB runs code
- scripts/docx_lib/editing/context.py 6.2 KB runs code
- scripts/docx_lib/editing/helpers.py 32 KB runs code
- scripts/docx_lib/editing/revisions.py 9.7 KB runs code
- scripts/docx_lib/editing/tests/test_xml_tolerance.py 4.7 KB runs code
- scripts/docx_lib/editing/xml_tolerance.py 3.3 KB runs code
- scripts/docx_lib/element_order.py 22 KB runs code
- scripts/docx_lib/schema_validation.py 5.7 KB runs code
- scripts/docx_lib/schemas/ecma/opc-contentTypes.xsd 1.9 KB
- scripts/docx_lib/schemas/ecma/opc-coreProperties.xsd 2.5 KB
- scripts/docx_lib/schemas/ecma/opc-digSig.xsd 2.8 KB
- scripts/docx_lib/schemas/ecma/opc-relationships.xsd 1.3 KB
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/dml-chart.xsd 73 KB
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/dml-chartDrawing.xsd 6.8 KB
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/dml-diagram.xsd 50 KB
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/dml-lockedCanvas.xsd 624 B
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/dml-main.xsd 148 KB
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/dml-picture.xsd 1.2 KB
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/dml-spreadsheetDrawing.xsd 8.7 KB
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/dml-wordprocessingDrawing.xsd 14 KB
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/pml.xsd 82 KB
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/shared-additionalCharacteristics.xsd 1.2 KB
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/shared-bibliography.xsd 7.2 KB
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/shared-commonSimpleTypes.xsd 6.2 KB
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/shared-customXmlDataProperties.xsd 1.2 KB
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/shared-customXmlSchemaProperties.xsd 880 B
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/shared-documentPropertiesCustom.xsd 2.5 KB
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/shared-documentPropertiesExtended.xsd 3.4 KB
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/shared-documentPropertiesVariantTypes.xsd 7.3 KB
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/shared-math.xsd 23 KB
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/shared-relationshipReference.xsd 1.3 KB
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/sml.xsd 237 KB
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/vml-main.xsd 26 KB
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/vml-officeDrawing.xsd 25 KB
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/vml-presentationDrawing.xsd 535 B
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/vml-spreadsheetDrawing.xsd 5.6 KB
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/vml-wordprocessingDrawing.xsd 3.9 KB
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/wml.xsd 167 KB
- scripts/docx_lib/schemas/ISO-IEC29500-4_2016/xml.xsd 4.5 KB
- scripts/docx_lib/schemas/mce/mc.xsd 3.1 KB
- scripts/docx_lib/schemas/microsoft/wml-2010.xsd 26 KB
- scripts/docx_lib/schemas/microsoft/wml-2012.xsd 3.7 KB
- scripts/docx_lib/schemas/microsoft/wml-2018.xsd 901 B
- scripts/docx_lib/schemas/microsoft/wml-cex-2018.xsd 1.7 KB
- scripts/docx_lib/schemas/microsoft/wml-cid-2016.xsd 1002 B
- scripts/docx_lib/schemas/microsoft/wml-sdtdatahash-2020.xsd 600 B
- scripts/docx_lib/schemas/microsoft/wml-symex-2015.xsd 745 B
- scripts/lint_docx_js.py 25 KB runs code
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.
- yesterday First seen · 145 lines · 50 tokens per session scan A aa8600d580d5
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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
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…