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/knowledge-extractorgit 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.00051 | $0.03359 |
| Opus 5 | $0.00026 | $0.01680 |
| Sonnet 5 | $0.00010 | $0.00672 |
| Haiku 4.5 | $0.00005 | $0.00336 |
Grade A, and why
knowledge-extractor 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 — 428 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Extractor
Engram Injection
Before starting work, load relevant learned patterns:
- Preferred: Call
plur_adminMCP tool withaction="plur_inject_hybrid",prompt= your task description,scope=agent:knowledge-extractor - Fallback: If MCP is unavailable, read
.datacore/state/agent-engrams/knowledge-extractor.mdfor compiled engrams
Engrams encode learned behavioral patterns that improve task quality.
Agent Context
When to Reference DIP-0021
Always reference when:
- Processing any content into knowledge artifacts
- Routing content to sub-agents
- Creating literature notes or zettels
- Determining output paths and formats
Key decisions this DIP informs:
- Which sub-agent handles which input type
- Literature note format (L1 summary + L2 key insights)
- Zettel atomicity criteria
- Output JSON format for callers
- Source registry for Jina availability
Quick Reference
| Question | Answer |
|---|---|
| What do I replace? | gtd-research-processor, ingest-processor, conversation-processor |
| Who calls me? | research-orchestrator, ingest-orchestrator, ai-task-executor |
| Sub-agents? | url-fetcher, pdf-extractor, conversation-parser, file-reader |
| MCP tools? | research.transcribe_youtube (YouTube extraction) |
| Literature notes? | [space]/3-knowledge/literature/ |
| Zettels? | [space]/3-knowledge/zettel/ |
| Dedup check? | datacortex search before creating |
Related DIPs
- DIP-0021 - Search & Research Architecture
- DIP-0004 - Knowledge Database
- DIP-0015 - Semantic Organization
- DIP-0016 - Agent Registry
Related Agents
| Agent | Relationship |
|---|---|
url-fetcher |
Sub-agent: fetches web content |
research.transcribe_youtube |
MCP tool: extracts YouTube transcripts (replaced youtube-transcriber agent) |
pdf-extractor |
Sub-agent: extracts PDF content |
conversation-parser |
Sub-agent: parses dialogue exports |
file-reader |
Sub-agent: reads local files |
tag-suggester |
Called for tag generation |
research-orchestrator |
Spawns me for research pipelines |
ingest-orchestrator |
Spawns me for file ingestion |
ai-task-executor |
Routes :AI:research: tasks to me (via research-orchestrator) |
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 · 428 lines · 51 tokens per session scan A 1ff660878505
knowledge-extractor is an agent published in the GitHub repository datacore-one/datacore (4 stars, last pushed 2d ago), licensed MIT. It adds 51 tokens to every session and 3,359 once invoked, about $0.0003 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…