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/seifbenayed/cloclo/docxnpx skills add SeifBenayed/cloclo --skill docxgit clone --depth 1 https://github.com/SeifBenayed/clocloWhat 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.00168 | $0.06275 |
| Opus 5 | $0.00084 | $0.03138 |
| Sonnet 5 | $0.00034 | $0.01255 |
| Haiku 4.5 | $0.00017 | $0.00628 |
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 2d 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.
This is a copy
73% identical to docx — 192 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 640 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DOCX creation, editing, and analysis
Tool-First Workflow
Use the Document tool for ALL operations. Do NOT use Python scripts unless you need features the tool doesn't have.
Available Document tool actions
| Task | Tool call |
|---|---|
| Inspect metadata | Document { action: "inspect", file_path: "doc.docx" } |
| Read text content | Document { action: "read_text", file_path: "doc.docx" } |
| Extract headings | Document { action: "extract_headings", file_path: "doc.docx" } |
| Extract HTML | Document { action: "extract_html", file_path: "doc.docx" } |
| Export as plain text | Document { action: "export_text", file_path: "doc.docx", output_path: "out.txt" } |
| Create new document | Document { action: "create", output_path: "doc.docx", content: {...} } |
| Unpack for XML editing | Document { action: "unpack", file_path: "doc.docx", output_path: "unpacked/" } |
| Repack after editing | Document { action: "pack", file_path: "unpacked/", output_path: "output.docx" } |
Creating a new document
Document { action: "create", output_path: "report.docx", content: {
"title": "Quarterly Report",
"sections": [
{
"heading": "Executive Summary",
"paragraphs": ["Revenue grew 15% YoY.", {"text": "Key highlight", "bold": true}]
},
{
"heading": "Financial Data",
"table": [["Metric", "Q1", "Q2"], ["Revenue", "100k", "115k"], ["Costs", "80k", "85k"]]
}
]
}}
Editing an existing document
Document { action: "unpack", file_path: "template.docx", output_path: "/tmp/unpacked/" }
# → Edit XML files in /tmp/unpacked/word/document.xml with the Edit tool
Document { action: "pack", file_path: "/tmp/unpacked/", output_path: "output.docx" }
When to fall back to Python/Bash
- Converting legacy .doc → .docx (requires LibreOffice)
- Accepting tracked changes (requires LibreOffice macro)
- XML validation against OOXML schemas
- Adding comments with commentsExtended/commentsIds (complex XML)
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.
- 2d ago First seen · 640 lines · 168 tokens per session scan A 9ee0813b4a62
docx is a skill published in the GitHub repository SeifBenayed/cloclo (114 stars, last pushed 4mo ago), licensed MIT. It adds 168 tokens to every session and 6,275 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 73% identical to docx, differing in 192 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…