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 decocms/studio --skill docxgit clone --depth 1 https://github.com/decocms/studioWrote 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/decocms/studio/docx)<a href="https://agentmods.dev/skills/decocms/studio/docx"><img src="https://agentmods.dev/badge/skills/decocms/studio/docx/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/decocms/studio/docx"><img src="https://agentmods.dev/badge/skills/decocms/studio/docx.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.00034 | $0.00183 |
| Opus 5.5 | $0.00014 | $0.00073 |
| Sonnet 5.5 | $0.00007 | $0.00037 |
| Haiku 4.5 | $0.00003 | $0.00018 |
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 21d 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.
What it actually says
docx — Word documents
Use this skill to read or summarize .docx files.
Scripts
extract.py
Print text content from a .docx as plain text. Paragraphs are separated by
blank lines; tables are rendered with tab-separated cells.
python /app/org/public/core/docx/extract.py <path-to-file.docx>
Direct python-docx usage
For headings, styles, tables, images, or editing, import docx directly. The
library is preinstalled.
from docx import Document
doc = Document("/path/to/file.docx")
for paragraph in doc.paragraphs:
...
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.
- 21d ago Changed 8ef5ca9e45ec
- 1mo ago First seen · 32 lines · 34 tokens per session scan A a3833585d200
docx is a skill published in the GitHub repository decocms/studio (412 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 183 once invoked, about $0.0001 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
csv-workbench
Analyze CSV files in /mnt/data and return concise numeric summaries.
review-artifact-comments
Only use when the user explicitly invokes this skill by name.
Workspace Data Analyst
Analyze CSV files in the workspace and summarize insights.
release-sync
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.
documentation-patterns
Technical documentation patterns for READMEs, ADRs, API docs (OpenAPI 3.1), changelogs, and writing style guides. Use when creating project documentation, writing architecture decisions, documenting APIs, or maintaining changelogs.
meter-invoice
Generate CocoMeter chargeback invoices. Usage: $meter invoice.