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 CodeInfinity1/Stram --skill docx-operationsgit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/docx-operations)<a href="https://agentmods.dev/skills/codeinfinity1/stram/docx-operations"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/docx-operations/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/codeinfinity1/stram/docx-operations"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/docx-operations.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00031 | $0.00467 |
| Opus 5.5 | $0.00012 | $0.00187 |
| Sonnet 5.5 | $0.00006 | $0.00093 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
docx-operations 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DOCX Operations
Purpose
Support Word document work while respecting current native capability boundaries. Stram can read/write local files and run approved Python analysis; a dedicated DOCX adapter should be implemented natively before claiming full Word automation.
When To Use
Use for DOCX planning, drafting content for Word, reading provided document text, preparing conversion workflows, or implementing/reviewing a native DOCX tool.
Inputs And Evidence
- DOCX path, desired edits, source text, formatting requirements, and output path.
- Available Python libraries or future native DOCX tool status.
Tool Map
docx_document_createdocx_document_inspectread_filewrite_notepython_interpreterpython_interpreter_artifacttool_searchcapability_surface
Workflow
- Use
docx_document_createfor structured local DOCX artifacts. - Use
docx_document_inspectto verify generated or provided DOCX files. - Keep document structure explicit: headings, tables, lists, styles, comments.
- Use approved Python only for capabilities not covered by the native DOCX tools.
- Verify generated artifacts by file existence and, where possible, rendered/parsed content.
- Report unsupported operations honestly.
Native Implementation Boundaries
- Do not import Anthropic DOCX skill code or external reference document scripts.
- Dedicated DOCX helpers are Stram-owned, tested, and schema-bound.
- Upstream document skills are reference evidence only.
Safety And Approval
- Documents may contain private data.
- Do not overwrite source files without explicit instruction.
- Preserve formatting requirements and review output before delivery.
Verification
- Confirm output path and artifact size/content.
- Note if visual/render verification was not available.
- Validate edits against the requested change list.
Failure Modes
- Claiming Word formatting was preserved without inspection.
- Corrupting a DOCX by treating it as plain text.
- Hiding missing adapter support.
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 First seen · 68 lines · 31 tokens per session scan A 246568916961
docx-operations is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 467 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-09-03.
Other skills, from other repositories
sif-to-csv
Parse a SIF (Standard Interchange Format) input into a readable preview and optionally append canonical product rows to the project's CSV library. Use when asked to convert or inspect SIF dealer data. For the reverse direction use /as:csv-to-sif.
impact-report-writer
Nonprofit/NGO impact report generation with data visualization suggestions, outcome metrics, narrative structure, and program data presentation. Use when writing impact reports, annual reports, or program evaluation summaries.
meeting-minutes-taker
Turn meeting transcripts into accurate minutes with decisions, actions, owners, and source evidence; also review or merge minutes and resolve speaker ambiguity.
awesome-docs
Generate, convert, and maintain animated GitHub-safe Markdown documents with animated SVG diagrams. Covers four SVG patterns (architecture flow, lifecycle loop, field carousel, timeline phases), guided interview for any doc type (README, architecture guide, runbook, API reference, tutorial, RFC, post-mortem…
latex-polish
Inspect a cleanly compiling LaTeX document for source pathologies and rendered visual defects by linting and viewing selected PDF pages. Use when compilation succeeds but title pages, floats, tables, figures, or layout still need publication-quality review. Not for basic compilation health; use $latex-health-check.
bib-coverage
Compare a project .bib against a Paperpile project/topic folder to find uncited papers or unfiled entries. Use when the user asks to compare a project .bib against a Paperpile project/topic folder to find uncited papers or unfiled entries.