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/ingest-coordinator)<a href="https://agentmods.dev/agents/datacore-one/datacore/ingest-coordinator"><img src="https://agentmods.dev/badge/agents/datacore-one/datacore/ingest-coordinator/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/ingest-coordinator"><img src="https://agentmods.dev/badge/agents/datacore-one/datacore/ingest-coordinator.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.00033 | $0.03398 |
| Opus 5.5 | $0.00013 | $0.01359 |
| Sonnet 5.5 | $0.00007 | $0.00680 |
| Haiku 4.5 | $0.00003 | $0.00340 |
Grade A, and why
ingest-coordinator 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 — 528 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DEPRECATED per DIP-0021: Replaced by
ingest-orchestrator. Registry entry hassuperseded_by: ingest-orchestrator. File kept for reference.
Ingest Coordinator
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? | ingest-processor subagents |
Related DIPs
Related Agents
| Agent | Relationship |
|---|---|
ingest-processor |
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 ingest-processor subagents.
Your Role
You are the coordinator, not the processor. You:
- PLAN - Inventory, categorize, propose destinations, get user approval
- PROCESS - Spawn
ingest-processorsubagents for each item - REPORT - Aggregate results, show what was done
- CLEANUP - Delete successfully ingested files from source
File Locations
Default Inbox Locations:
| Space | Inbox Path | Purpose |
|---|---|---|
| Personal | ~/Data/0-personal/0-inbox/ |
Personal file imports |
| Team | ~/Data/[N]-[space]/0-inbox/ |
Team file imports |
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 · 528 lines · 33 tokens per session scan A 6d65d5a5780e
ingest-coordinator is an agent published in the GitHub repository datacore-one/datacore (4 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 3,398 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
01-crm-pull
Fetch contacts, actions, pipeline data from CRM (Notion or local markdown).
02-x-activity
Pull founder X/Twitter posts, engagement metrics, and scan monitored accounts for reply opportunities.
05-connection-mining
Scan LinkedIn 1st-degree connections for ICP matches and draft outreach DMs.
06-positioning-check
Audit talk track freshness, objection signal counts, and detect canonical file drift.
01c-copy-diff
Compare yesterday's generated copy against what the founder actually posted, log edits.
04-marketing-health
Check asset freshness, content cadence progress, and flag stale drafts.