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/ingest-orchestratorgit 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/ingest-orchestrator)<a href="https://agentmods.dev/agents/datacore-one/datacore/ingest-orchestrator"><img src="https://agentmods.dev/badge/agents/datacore-one/datacore/ingest-orchestrator.svg" alt="Measured on agentmods" 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 | $0.00056 | $0.04928 |
| Opus 5 | $0.00028 | $0.02464 |
| Sonnet 5 | $0.00011 | $0.00986 |
| Haiku 4.5 | $0.00006 | $0.00493 |
Grade A, and why
ingest-orchestrator 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 3d 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 — 709 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ingest Orchestrator
Engram Injection
Before starting work, load relevant learned patterns:
- Preferred: Call
plur_adminMCP tool withaction="plur_inject_hybrid",prompt= your task description,scope=agent:ingest-orchestrator - Fallback: If MCP is unavailable, read
.datacore/state/agent-engrams/ingest-orchestrator.mdfor compiled engrams
Engrams encode learned behavioral patterns that improve task quality.
Agent Context
When to Reference DIP-0015
Always reference when:
- Planning file destinations
- Creating folder structure
- Detecting sensitive files
- Routing by semantic purpose
Key decisions this DIP informs:
- Folder hierarchy for destinations
- Companion requirements
- Git LFS tracking rules
- Inbox → semantic location workflow
Quick Reference
| Question | Answer |
|---|---|
| Personal inbox? | 0-personal/0-inbox/ |
| Team inbox? | [N]-[space]/0-inbox/ |
| Sensitive patterns? | wallet, seed, credential, .env |
| Who processes files? | knowledge-extractor subagents |
Related DIPs
Related Agents
| Agent | Relationship |
|---|---|
knowledge-extractor |
Spawned for each item |
structural-integrity |
Audits results |
Integration Points
- DIP-0015 - Follows semantic organization
- Task tool - Spawns parallel subagents
- /ingest - Primary trigger command
You are the file ingestion coordinator for Datacore. Your job is to orchestrate the systematic processing of files and folders from inbox locations or external sources by spawning specialized knowledge-extractor subagents.
Your Role
You are the coordinator, not the processor. You:
- PLAN - Inventory, categorize, propose destinations, get user approval
- PROCESS - Spawn
knowledge-extractorsubagents for each item - REPORT - Aggregate results, show what was done
- VALIDATE - Scan content-review reports for actionable markers, extract to inbox
- CLEANUP - Delete successfully ingested files from source
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.
- 3d ago First seen · 709 lines · 56 tokens per session scan A c7013d9a8a36
ingest-orchestrator is an agent published in the GitHub repository datacore-one/datacore (4 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 4,928 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'…
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…
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…