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 skills/datacore-one/datacore/research-statusnpx skills add datacore-one/datacore --skill research-statusgit 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/skills/datacore-one/datacore/research-status)<a href="https://agentmods.dev/skills/datacore-one/datacore/research-status"><img src="https://agentmods.dev/badge/skills/datacore-one/datacore/research-status.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.00019 | $0.00163 |
| Opus 5 | $0.00010 | $0.00081 |
| Sonnet 5 | $0.00004 | $0.00033 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
research-status 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 today.
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.
What it actually says
Research Status
Instructions
Follow the full workflow in ~/Data/.datacore/modules/research/commands/research-status.md.
Show:
- Research queue - Count pending URLs in research_learning.org
- Recent podcasts - Last 5 generated podcasts with dates
- Knowledge base growth - Literature notes, zettels, landscape entries counts
- Readwise items - Pending items to import (if configured)
- Failed URLs - Any URLs that failed processing
Display as formatted dashboard. Offer: import Readwise, run /research-daily, retry failed URLs.
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.
- today First seen · 21 lines · 19 tokens per session scan A 167c81a7c65d
research-status is a skill published in the GitHub repository datacore-one/datacore (4 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 163 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-09-03.
Other skills, from other repositories
forgetful-remember
Remember knowledge worth keeping — a decision made, a solution found, a preference stated, a pattern confirmed. Use when work surfaces something future sessions will need, or the user asks to remember something. Routes content to the right store (memory, document, code artifact, entity, procedure, file) and enforces…
add-editor
Wire Deus's memory + evolution layers into an external code editor (Zed and other ACP/MCP clients) so the editor's own agent gains Deus's vault recall and self-improving reflexion loop. Configuration only — no new code. Triggers on "add editor", "use Deus in my editor", "zed integration", "editor integration", "wire…
memcord
Privacy-first, self-hosted chat memory for OpenClaw — save and recall conversation history across sessions without any cloud dependency.
hipocampus-compaction
Build 5-level compaction tree (daily/weekly/monthly/root) with smart thresholds and fixed/tentative lifecycle. Run at session start when triggers are met, or via external scheduler.
hipocampus-core
3-tier agent memory system with 5-level compaction tree. Codex CLI version. Defines session start protocol, end-of-task checkpoints, and memory file management. MUST be followed every session.
hipocampus-search
Search memory using qmd (BM25 + optional vector) and compaction tree traversal. Use ROOT.md to decide whether to search memory or look externally. Always check memory before external lookups.