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 commands/datacore-one/datacore/research-dailygit 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/commands/datacore-one/datacore/research-daily)<a href="https://agentmods.dev/commands/datacore-one/datacore/research-daily"><img src="https://agentmods.dev/badge/commands/datacore-one/datacore/research-daily.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.00008 | $0.01381 |
| Opus 5 | $0.00004 | $0.00691 |
| Sonnet 5 | $0.00002 | $0.00276 |
| Haiku 4.5 | $0.00001 | $0.00138 |
Grade A, and why
research-daily 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/research-daily
Command Context
When to Reference Research Module
Always reference when:
- User wants immediate processing instead of waiting for nightshift
- Testing the research pipeline during development
- Processing urgent research that can't wait until overnight
- Need to clear research queue before end of day
- Troubleshooting research processing issues
Key decisions this command informs:
- Whether to process all items or specific section/batch
- Whether to generate podcasts immediately or skip for nightshift
- Whether to extract action items and update CRM during processing
- How to handle URL failures (retry, skip, mark cancelled)
Quick Reference
| Question | Answer |
|---|---|
| What does it process? | TODO items from research_learning.org (all, by section, or limited batch) |
| Does it generate podcasts? | Configurable - can skip if nlm unavailable |
| What's the processing limit? | max_sources_per_night setting (default 20) |
| What outputs are created? | Literature notes, zettels, action items, journal updates, landscape entries |
Agents This Command Invokes
| Agent | Purpose |
|---|---|
| research-orchestrator | Orchestrates entire processing pipeline with user-specified scope and options |
Integration Points
- research-orchestrator agent - Invoked with processing scope (all/section/limited)
- research_learning.org - Input source scanned for TODO items
- User confirmation - Interactive prompts for scope and settings
- Processing summary - Results presented with follow-up action suggestions
- nlm availability - Checks if podcast generation is possible
- Module settings - Respects action_extraction, post_processing, max_links settings
Manually trigger daily research processing outside of nightshift.
When to Use
- You want to process research links immediately (not wait for nightshift)
- Testing the research pipeline
- Processing a specific batch of links
Workflow
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 · 238 lines · 8 tokens per session scan A 57212d3e2580
research-daily is a command published in the GitHub repository datacore-one/datacore (4 stars, last pushed today), licensed MIT. It adds 8 tokens to every session and 1,381 once invoked, about $0.0000 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 commands, from other repositories
prd-archive
Archive the active PRD (blocked until every accepted finding has a receipt).
prd-map
Build a codebase map so PRDs are written with repo context, not blind.
prd-split
Split the approved PRD into one issue spec per manifest entry.
prd-os-init
Initialize prd-os in this repo (writes .prd-os/config.json).
rca-check
Lint an RCA or premortem document against the canonical template.
prd-approve
Advance the active PRD to approved (blocked by pending findings).