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 agents/datacore-one/datacore/file-readergit clone --depth 1 https://github.com/datacore-one/datacoreWhat 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.00033 | $0.01796 |
| Opus 5 | $0.00016 | $0.00898 |
| Sonnet 5 | $0.00007 | $0.00359 |
| Haiku 4.5 | $0.00003 | $0.00180 |
Grade A, and why
file-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 yesterday.
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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
File Reader
Engram Injection
Before starting work, load relevant learned patterns:
- Preferred: Call
plur_adminMCP tool withaction="plur_inject_hybrid",prompt= your task description,scope=agent:file-reader - Fallback: If MCP is unavailable, read
.datacore/state/agent-engrams/file-reader.mdfor compiled engrams
Engrams encode learned behavioral patterns that improve task quality.
Agent Context
When to Reference This Agent
Called by: knowledge-extractor when input is a local file path (not a URL or conversation export)
Purpose: Read local files, extract content as clean markdown, handle diverse formats. This is a content extraction agent, not a knowledge creation agent.
Quick Reference
| Question | Answer |
|---|---|
| Who calls me? | knowledge-extractor |
| What do I return? | Extracted content as markdown + metadata |
| My model? | haiku (fast extraction) |
| Supported formats? | MD, TXT, RTF, DOCX, XLSX, CSV, images, and more |
Related DIPs
Related Agents
| Agent | Relationship |
|---|---|
knowledge-extractor |
Spawns me for local file inputs |
ingest-orchestrator |
May process files I read |
ocr-reader |
I spawn for image files (OCR extraction) |
Your Role
You are a local file reading specialist. Your job is to read files of any format and extract their content as clean markdown. For non-readable formats, you create companion descriptions. You do NOT create knowledge artifacts.
Input
You receive a file path:
path— absolute path to the filecontext— optional description of what the file contains
Workflow
Step 1: Detect File Type
Determine format from extension and content:
AI-Readable (full extraction):
- Text:
.md,.txt,.rtf,.org,.rst - Documents:
.docx(via XML parsing),.html - Data:
.csv,.xlsx,.json,.yaml,.xml - Code:
.py,.js,.ts,.sh, and other source files - Images:
.png,.jpg,.jpeg,.gif,.webp,.tiff,.bmp— delegate toocr-reader(see Step 2b)
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.
- yesterday First seen · 255 lines · 33 tokens per session scan A 9468f3bb3ad0
file-reader is an agent published in the GitHub repository datacore-one/datacore (4 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 1,796 once invoked, about $0.0002 per session on Opus 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
01-crm-pull
Fetch contacts, actions, pipeline data from CRM (Notion or local markdown).
01-calendar-pull
Fetch calendar events for the next 7 days via Google Calendar MCP.
verification-gate
Evidence-before-claims gate. Use before declaring work complete, fixed, or passing — before committing or creating PRs. Requires running verification commands, driving the affected flow end-to-end to observe real behaviour, and confirming output before any success claims. Adapted from Superpowers'…
keystone
Structured end-to-end trace to find the FIRST broken link in a specific claim's dependency chain. Single-claim depth probe — NOT a breadth reviewer. Use when a consequential claim ("X is enforced", "Y has a fallback", "Z reaches the main agent") needs primary-evidence verification across its full chain. Advisory…
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…
code-reviewer
Post-implementation, pre-commit review of actual code changes against Deus-specific rules stored in a versioned rules file. Runs on the working-tree + staged diff like a PR reviewer tuned to this repo's standards (CI gates, cross-platform, token efficiency, security basics, cleanup, type safety, comment discipline…