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/process-inboxgit 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/process-inbox)<a href="https://agentmods.dev/commands/datacore-one/datacore/process-inbox"><img src="https://agentmods.dev/badge/commands/datacore-one/datacore/process-inbox.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.00756 |
| Opus 5 | $0.00004 | $0.00378 |
| Sonnet 5 | $0.00002 | $0.00151 |
| Haiku 4.5 | $0.00001 | $0.00076 |
Grade A, and why
process-inbox 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/process-inbox
Automated inbox processing — classify and route all entries from inbox.org.
When to Use
- Nightshift scheduled execution (01:00 UTC nightly)
- Manual batch processing when inbox is full
- After email triage has added new items
Mode Detection
Nightshift mode (no user present): Process all items autonomously. Make classification decisions without asking. Use conservative defaults — when uncertain, route to next_actions.org rather than deleting.
Interactive mode (user present): Ask for confirmation on ambiguous items.
Workflow
Step 1: Read inbox.org
Read 0-personal/org/inbox.org and count entries under * Inbox.
If 0 entries: log "Inbox empty" and exit.
Step 2: Process Each Entry
For each entry under * Inbox, spawn gtd-inbox-processor subagent with:
- The entry text
- Target files:
next_actions.org,research_learning.org,ideas.org - Mode: autonomous (no user confirmation needed)
Classification rules (from gtd-inbox-processor):
- URL/link with "read/review/check out" →
research_learning.orgunder matching focus area - Actionable task →
next_actions.orgunder matching focus area - Idea/exploration →
ideas.orgwith scoring - Reference → knowledge note or next_actions with
:reference:tag - Bookmarks with notes/instructions → preserve the notes as CONTEXT property
Step 3: Route Research Items
For items routed to research_learning.org:
- Place under the correct focus area heading (Verity, Trading, Health, Technology, etc.)
- Format as:
*** TODO [#B] Title or description :PROPERTIES: :CREATED: [YYYY-MM-DD Day] :SOURCE: URL or reference :EFFORT: 0:20 :END: Link: https://... Why: [extracted relevance from bookmark notes] - Preserve any user notes or instructions from the original bookmark
Step 4: Commit Results
After all entries processed:
- Verify inbox.org entries have been removed (routed elsewhere)
- Count items routed to each destination
- Git commit and push
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 · 104 lines · 8 tokens per session scan A ff5b6b6b2496
process-inbox 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 756 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-review
Review the active PRD with Codex and stream normalized findings to JSONL.
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.
rca-check
Lint an RCA or premortem document against the canonical template.
prd-os-init
Initialize prd-os in this repo (writes .prd-os/config.json).
prd-approve
Advance the active PRD to approved (blocked by pending findings).