Borrowing it
Nothing to install: this file belongs to yukiyokotani/office-open-xml-viewer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/yukiyokotani/office-open-xml-viewer/main/.agents/skills/docx-architecture-audit/SKILL.mdgit clone --depth 1 https://github.com/yukiyokotani/office-open-xml-viewerWrote 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/yukiyokotani/office-open-xml-viewer/docx-architecture-audit)<a href="https://agentmods.dev/skills/yukiyokotani/office-open-xml-viewer/docx-architecture-audit"><img src="https://agentmods.dev/badge/skills/yukiyokotani/office-open-xml-viewer/docx-architecture-audit/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/yukiyokotani/office-open-xml-viewer/docx-architecture-audit"><img src="https://agentmods.dev/badge/skills/yukiyokotani/office-open-xml-viewer/docx-architecture-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00055 | $0.00668 |
| Opus 5 | $0.00028 | $0.00334 |
| Sonnet 5 | $0.00011 | $0.00134 |
| Haiku 4.5 | $0.00006 | $0.00067 |
Grade A, and why
docx-architecture-audit 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 12d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DOCX Architecture Audit
Audit semantics that static identifier checks cannot prove. Report only evidence-backed findings with an exact code reference or a reproducible command.
Workflow
-
Read
AGENTS.mdanddocs/docx-layout-engine-redesign.mdcompletely. -
Inspect the complete change against
main; do not limit review to the latest commit. Read the owning modules and focused tests, not only the diff. -
Consult the relevant local
spec/material before judging OOXML behavior. Prefer ECMA-376 / ISO/IEC 29500, then the applicable Microsoft implementation note. Do not disclose private sample contents or paths. -
Run the deterministic gates:
mise exec -- node scripts/check-docx-layout-boundaries.mjs --final mise exec -- pnpm test:docx-boundaries mise exec -- pnpm test:docx-compatibility mise exec -- pnpm test:docx-public-api mise exec -- pnpm test:docx-package-build mise exec -- pnpm typecheck git diff --check -
Audit the final dependency direction and runtime behavior:
- one production layout algorithm exists for each supported feature class;
- parser facts flow into immutable point-space layout and then measurement-free paint;
- paint performs no measurement, shaping, style resolution, pagination, or parser-model access, including through transitive imports;
- parser objects and retained layouts are not mutated or runtime-stamped;
- no migration flag, silent legacy fallback, dry-render geometry collection, or transitional allowance remains;
- body, stories, tables, text boxes, and supported floating content participate
in
DocumentLayoutand preserve page/layer ownership; - main and worker use the same contracts and stable layout fingerprints;
- compatibility decisions are isolated with exact evidence, while normative rules and unsupported diagnostics are not mislabeled as observations;
renderer.tsremains a thin adapter with no hidden layout or paint algorithm;- public declarations remain compatible;
- shared OOXML primitives live in
coreorooxml-commononly when the abstraction is genuinely cross-format.
What ships with it
1 file 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.
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.
- 12d ago First seen · 60 lines · 55 tokens per session scan A 29f62e071c71
docx-architecture-audit is a skill published in the GitHub repository yukiyokotani/office-open-xml-viewer (790 stars, last pushed 3d ago), licensed MIT. It adds 55 tokens to every session and 668 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-30.
Other skills, from other repositories
brand-docx
Brand-aware Word engine. Use to (1) EXTRACT a company's brand from a Word template into a reusable "Brand Profile", (2) COMPREHEND the template with the model (optional), (3) VERIFY it, (4) GENERATE new on-brand .docx documents FROM a saved profile. Trigger on "extract our brand", "learn/match this template", "use our…
brand-pptx
Brand-aware PowerPoint engine. Use to (1) EXTRACT a company's brand from a .pptx template into a reusable "Brand Profile", (2) COMPREHEND the template with the model (optional), (3) VERIFY it, (4) GENERATE a new on-brand .pptx from an IntermediateDocument. Trigger on "extract our brand", "use our deck template"…
brand-xlsx
Brand-aware Excel engine. Use to (1) EXTRACT a company's brand from a .xlsx template into a reusable "Brand Profile", (2) COMPREHEND the template with the model (optional), (3) VERIFY it, (4) GENERATE a new on-brand .xlsx from a GridDocument fill manifest. Trigger on "extract our brand", "use our workbook template"…
document-generation
Generate Word (.docx), Excel (.xlsx) and PowerPoint (.pptx) documents and fill existing PDF forms, from real NetClaw data, with per-element provenance and no fabrication. Use when someone needs a deliverable rather than an answer — a change record to attach to a CR, an audit workbook for a compliance reviewer, a…
office-artifacts
Manage Office files, formats and versions; use Writer, Calc or Impress for content.
document-processing-expert
Read, generate and modify office documents and PDFs from code: PDF extraction and forms, Word documents, Excel workbooks and PowerPoint decks. Use when the user mentions PDF, DOCX, XLSX, PPTX, Word, Excel, PowerPoint or spreadsheets, wants data extracted from documents, needs a report or invoice generated as a file…