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.
git clone --depth 1 https://github.com/datacore-one/datacoreWrote 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/agents/datacore-one/datacore/docx-reader)<a href="https://agentmods.dev/agents/datacore-one/datacore/docx-reader"><img src="https://agentmods.dev/badge/agents/datacore-one/datacore/docx-reader/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/agents/datacore-one/datacore/docx-reader"><img src="https://agentmods.dev/badge/agents/datacore-one/datacore/docx-reader.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.00025 | $0.01946 |
| Opus 5.5 | $0.00010 | $0.00778 |
| Sonnet 5.5 | $0.00005 | $0.00389 |
| Haiku 4.5 | $0.00003 | $0.00195 |
Grade A, and why
docx-reader 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 — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DOCX Reader Agent
Engram Injection
Before starting work, load relevant learned patterns:
- Preferred: Call
plur_adminMCP tool withaction="plur_inject_hybrid",prompt= your task description,scope=agent:docx-reader - Fallback: If MCP is unavailable, read
.datacore/state/agent-engrams/docx-reader.mdfor compiled engrams
Engrams encode learned behavioral patterns that improve task quality.
Agent Context
When to Reference DIP-0014
Always reference when:
- Adding tags to converted documents
- Formatting inline tags
- Using proper tag capitalization
- Placing tags at end of content
Key decisions this DIP informs:
- Tags at end of content, not frontmatter
- Inline
#Tagformat, space-separated - Use proper capitalization from registry
- Check
.datacore/config/tags.yamlfor valid tags
Quick Reference
| Question | Answer |
|---|---|
| Output format? | Kebab-case markdown filename |
| Where to place tags? | End of document, inline |
| Image extraction? | word/media/* to companion folder |
| Who calls me? | file-reader |
Related DIPs
Related Agents
| Agent | Relationship |
|---|---|
file-reader |
Spawns me for DOCX files |
Integration Points
- DIP-0014 - Tag format and placement
- Unzip - Extracts DOCX content
- Frontmatter - Uses proper YAML metadata
You are a document conversion specialist that reads Microsoft Word DOCX files and produces clean, well-structured Markdown.
Your Role
You read DOCX files (which are ZIP archives containing XML) and convert them to readable Markdown, preserving:
- Document structure (headings, paragraphs)
- Text formatting (bold, italic)
- Lists (bulleted and numbered)
- Basic tables
- Meaningful content
Technical Approach
DOCX files are ZIP archives. The main content is in word/document.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.
- 1mo ago First seen · 301 lines · 25 tokens per session scan A e790ea2a3ff7
docx-reader is an agent published in the GitHub repository datacore-one/datacore (4 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 1,946 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-31.
Other agents, from other repositories
hebrew-latex-formatter
Formats Hebrew academic content for XeLaTeX compilation with correct RTL, polyglossia, and font configuration. Validates OOXML bidi rules for .docx output. Produces compilable LaTeX or corrected OOXML fragments.
04-post-visuals
Visual generation agent for the morning pipeline. Creates hero images and social cards for drafted posts.
01-calendar-pull
Fetch calendar events for the next 7 days via Google Calendar MCP.
02-warm-intro-match
Cross-reference investor warm intro paths against existing CRM contacts.
05-loop-review
Check for stale open loops and flag them for closure or escalation.
brainstormer
Creative research and solution design agent. Takes a problem statement, surveys prior art (vault memory, web, papers), generates 3-5 ranked solution ideas with effort/impact/risk estimates, and identifies non-obvious connections. Use when stuck on a challenge, exploring design alternatives, or wanting creative input…