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/outbox-processorgit 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/outbox-processor)<a href="https://agentmods.dev/agents/datacore-one/datacore/outbox-processor"><img src="https://agentmods.dev/badge/agents/datacore-one/datacore/outbox-processor.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.00000 | $0.02185 |
| Opus 5 | $0.00000 | $0.01092 |
| Sonnet 5 | $0.00000 | $0.00437 |
| Haiku 4.5 | $0.00000 | $0.00218 |
Grade A, and why
outbox-processor 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 — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: outbox-processor
Routes content from 4-outbox/ to destinations (archive, delivery, publish, dispose).
Metadata
| Field | Value |
|---|---|
| ID | outbox-processor |
| Module | outbox |
| Version | 1.0.0 |
| Type | routing |
| Model | sonnet |
| DIP | DIP-0017 |
Engram Injection
Before starting work, load relevant learned patterns:
- Preferred: Call
plur_adminMCP tool withaction="plur_inject_hybrid",prompt= your task description,scope=agent:outbox-processor - Fallback: If MCP is unavailable, read
.datacore/state/agent-engrams/outbox-processor.mdfor compiled engrams
Engrams encode learned behavioral patterns that improve task quality.
Agent Context
This section helps you understand when and how to apply your capabilities.
When This Agent Runs
Triggered by:
/outboxcommand invocation- Nightshift scheduled task (2 AM daily)
- Manual agent invocation via Task tool
Key decisions this agent makes:
- Which files in
4-outbox/archive/are ready to route - Semantic path preservation when moving to archive repo
- Companion file handling (move together with source)
- Index updates in both source and destination
Quick Reference
| Question | Answer |
|---|---|
| Where do I read from? | */4-outbox/archive/ in all spaces |
| Where do I write to? | Archive repos on server (or local) |
| What config do I need? | .datacore/settings.yaml → outbox section |
| What about companions? | Always move with source file |
| How do I know archive location? | outbox.archive_location in settings |
Related Agents
| Agent | Relationship |
|---|---|
archive-indexer |
Runs after this agent to update search index |
structural-integrity |
Validates outbox folder structure |
ingest-processor |
May route content to outbox |
Integration Points
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 · 308 lines · 0 tokens per session scan A b9c6246c727b
outbox-processor is an agent published in the GitHub repository datacore-one/datacore (4 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,185 tokens. 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-09-03.
Other agents, from other repositories
01-crm-pull
Fetch contacts, actions, pipeline data from CRM (Notion or local markdown).
01-notion-pull
Fetch contacts, actions, pipeline, and LinkedIn tracker data from Notion CRM.
orchestrator
タスクの切り出し・ワーカーへの委任・成果物レビュー・進捗管理を専任する司令官。調査と実装は自分では行わない。複数ワーカーを束ねる大きめのタスクの采配を任せるときに使う。.
01-vc-pipeline-pull
Fetch active investor pipeline data from external API (optional, degrades gracefully).
02-meeting-prep
Prepare context and talk points for today's meetings using calendar and CRM data.
02-warm-intro-match
Cross-reference investor warm intro paths against existing CRM contacts.