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/commands/datacore-one/datacore/research-status)<a href="https://agentmods.dev/commands/datacore-one/datacore/research-status"><img src="https://agentmods.dev/badge/commands/datacore-one/datacore/research-status/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/commands/datacore-one/datacore/research-status"><img src="https://agentmods.dev/badge/commands/datacore-one/datacore/research-status.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.00006 | $0.02496 |
| Opus 5.5 | $0.00002 | $0.00998 |
| Sonnet 5.5 | $0.00001 | $0.00499 |
| Haiku 4.5 | $0.00001 | $0.00250 |
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 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 — 375 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/research-status
Command Context
When to Reference Research Module
Always reference when:
- Checking morning research pipeline health
- Before triggering manual processing with /research-daily
- Reviewing overnight nightshift results
- Monitoring knowledge base growth trends
- Diagnosing research processing issues
Key decisions this command informs:
- Whether to process pending items immediately or wait for nightshift
- Which focus areas need more research attention
- If URL failures need manual intervention
- Whether podcast generation is working correctly
Quick Reference
| Question | Answer |
|---|---|
| What does this show? | Queue counts, Readwise items, recent podcasts, knowledge base growth |
| What files does it read? | research_learning.org, podcasts/, literature/, zettel/, industry-landscape.yaml |
| Does it modify anything? | Can import Readwise items to research_learning.org if user confirms |
| What follow-up actions? | Import Readwise, /research-daily, retry failed URLs |
Agents This Command Invokes
None - this is a read-only status command that scans files and presents summaries.
Integration Points
- research_learning.org - Scans for TODO/DONE counts per section
- Readwise Reader API - Checks for archived items ready to import
- Podcast directory - Lists recent audio files with metadata
- Knowledge directories - Counts literature notes and zettels
- industry-landscape.yaml - Counts landscape entries
- /research-daily - Suggested as follow-up action for pending items
- Nightshift status - May reference /nightshift-status for diagnostics
View research queue, recent podcasts, and processing statistics.
When to Use
- Morning check on research pipeline status
- Before triggering manual processing
- Reviewing what was processed overnight
- Checking industry landscape growth
Workflow
Step 1: Gather Status
Scan the following sources:
research_learning.org- Count TODO/DONE items per sectionReadwise Reader API- Check for archived items (if configured)0-personal/content/podcasts/- List recent podcasts0-personal/notes/2-knowledge/literature/- Count literature notes0-personal/notes/2-knowledge/zettel/- Count zettelsindustry-landscape.yaml- Count entries
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 Changed f9cb8ef5e4b6
- 2mo ago First seen · 375 lines · 6 tokens per session scan A 1697fef1ba86
research-status is a command published in the GitHub repository datacore-one/datacore (4 stars, last pushed yesterday), licensed MIT. It adds 6 tokens to every session and 2,496 once invoked, about $0.0000 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-09-03.
research-status compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| research-statusdatacore-one/datacore | Command | 4 | yesterday | MIT | A | 6 | Claude Code |
| compresssliamh11/Deus | Command | 51 | 2d ago | MIT | A | 0 | Claude Code |
| voice-refreshassafkip/kipi-system | Command | 131 | 2d ago | MIT | A | 59 | Claude Code |
| checkpointsliamh11/Deus | Command | 51 | 2d ago | MIT | A | 0 | Claude Code |
| preservesliamh11/Deus | Command | 51 | 2d ago | MIT | A | 0 | Claude Code |
| statuslinxule/memex-plugin | Command | 7 | 2d ago | MIT | A | 15 | Claude Code |
| openlinxule/memex-plugin | Command | 7 | 2d ago | MIT | A | 11 | Claude Code |