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 skills add UseJunior/safe-docx --skill docx-editinggit clone --depth 1 https://github.com/UseJunior/safe-docxWrote 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/usejunior/safe-docx/docx-editing)<a href="https://agentmods.dev/skills/usejunior/safe-docx/docx-editing"><img src="https://agentmods.dev/badge/skills/usejunior/safe-docx/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.
<a href="https://agentmods.dev/skills/usejunior/safe-docx/docx-editing"><img src="https://agentmods.dev/badge/skills/usejunior/safe-docx/docx-editing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 64 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00109 | $0.04450 |
| Opus 5.5 | $0.00044 | $0.01780 |
| Sonnet 5.5 | $0.00022 | $0.00890 |
| Haiku 4.5 | $0.00011 | $0.00445 |
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 1mo 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 — 342 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 — once installed — runs entirely on the local filesystem with zero network activity.
Source Code and Audit
Safe-DOCX is fully open source (Apache-2.0 license). Review the complete source before installing:
- GitHub: https://github.com/UseJunior/safe-docx
- npm registry: https://www.npmjs.com/package/@usejunior/safe-docx
- Code coverage: Published via Codecov on every release
- Conformance harness: Automated spec coverage tests run in CI on every commit
- No postinstall scripts — verify:
npm view @usejunior/safe-docx scriptsshows nopostinstallorinstallhooks
All security claims below are verifiable by reading the source.
Runtime Requirements
Safe-DOCX requires these binaries to be available on the host:
| Binary | Minimum version | Why |
|---|---|---|
node |
18.0.0 | Authoritative version from packages/safe-docx/package.json engines field |
npx |
Bundled with npm | Used by the recommended MCP connector to launch the server |
If you prefer not to use npx, see Offline / Pinned Installation below for alternatives.
Safety Model
Safe-DOCX's safety model has two distinct phases: install time (when the package is fetched) and runtime (when the MCP server is running).
Install-Time Behavior (network required, one-time)
- npm registry fetch — the recommended connector command
npx -y @usejunior/safe-docxdownloads the package fromregistry.npmjs.orgon first run. Subsequent runs use the cached copy unless the cache is cleared. - No postinstall scripts — the package declares no
postinstall,preinstall, orinstallhooks. Verify withnpm view @usejunior/safe-docx scripts. - Provenance — releases are published with npm provenance (
--provenance), so you can verify the package was built from the public GitHub repo via GitHub Actions. - If you need guaranteed offline install — pin a specific version and vendor it locally. See the next section.
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.
- 1mo ago Changed 3f5a8bfb33eb
- 1mo ago First seen · 342 lines · 109 tokens per session scan A bf62bd5fa7ca
docx-editing is a skill published in the GitHub repository UseJunior/safe-docx (46 stars, last pushed 3d ago), licensed Apache-2.0. It adds 109 tokens to every session and 4,450 once invoked, about $0.0004 per session on Opus 5.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
pandadoc-signing-velocity
Build a signing pipeline report — status counts, average time to sign, value in flight, and documents that are stuck. Computed client-side with the sample size and method stated. Use when someone wants a weekly signing report or pipeline overview.
markitdown-file-intake
Use when the user provides a MarkItDown-supported file or URL and converting it to Markdown first will make inspection easier, cheaper, or more reliable.
defuddle
Use when the user provides a URL to a standard web page and clean Markdown extraction with Defuddle would reduce clutter and token cost.
nutrient-document-processing
Process, convert, OCR, extract, redact, sign, and fill documents using the Nutrient DWS API. Works with PDFs, DOCX, XLSX, PPTX, HTML, and images.
octoperf-export-bench-report-pdf
Use when the user asks to "export the report as PDF", "print the bench report", "get a PDF of report X", "export these reports", "share a PDF with stakeholders", or any variation that calls for a static artefact of one or several OctoPerf benchReports. Walks the LLM through the three-step async chain (submit print…
google-docs
Manage Google Docs and Google Drive with full document operations and file management. Includes Markdown support for creating formatted documents with headings, bold, italic, lists, tables, and checkboxes. Also supports Drive operations (upload, download, share, search).