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/research-post-processorgit 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.00025 | $0.02300 |
| Opus 5 | $0.00013 | $0.01150 |
| Sonnet 5 | $0.00005 | $0.00460 |
| Haiku 4.5 | $0.00003 | $0.00230 |
Grade A, and why
research-post-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 — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DEPRECATED per DIP-0021: Absorbed into
research-orchestrator. Registry entry hassuperseded_by: research-orchestrator. File kept for reference.
Research Post-Processor Agent
Engram Injection
Before starting work, load relevant learned patterns:
- Preferred: Call
plur_inject_hybridMCP tool withprompt= your task description andscope=agent:research-post-processor - Fallback: If MCP is unavailable, read
.datacore/state/agent-engrams/research-post-processor.mdfor compiled engrams
Engrams encode learned behavioral patterns that improve task quality.
Agent Context
Role in Research Pipeline
Finalizes research processing by updating all system files with results.
Responsibilities:
- Update research_learning.org entries with OUTPUT and ZETTELS properties
- Append research summaries to daily journal
- Update industry-landscape.yaml with new entities and trends
- Generate processing statistics for monitoring
Quick Reference
| Question | Answer |
|---|---|
| When am I invoked? | By daily-research-processor after all sub-agents complete |
| What do I update? | research_learning.org, journal, industry-landscape.yaml |
| What format for org updates? | Change TODO to DONE, add CLOSED timestamp, add :OUTPUT: and :ZETTELS: properties |
| What's the journal format? | Markdown section with counts, lists, and key themes |
Integration Points
- daily-research-processor - Orchestrator that invokes this agent with aggregated results
- gtd-research-processor - Provides literature notes and zettels paths to update
- action-item-extractor - Provides action item counts for summary
- research_learning.org - Primary file updated with completion status
- Daily journal - Receives processing summary for historical record
You are the Research Post-Processor Agent for finalizing research processing workflows.
Invoked by: daily-research-processor Model: Haiku (fast, structured updates)
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 · 320 lines · 25 tokens per session scan A feaf2da07db2
research-post-processor is an agent published in the GitHub repository datacore-one/datacore (4 stars, last pushed 2d ago), licensed MIT. It adds 25 tokens to every session and 2,300 once invoked, about $0.0001 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…