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/agents/datacore-one/datacore/gtd-process-inbox)<a href="https://agentmods.dev/agents/datacore-one/datacore/gtd-process-inbox"><img src="https://agentmods.dev/badge/agents/datacore-one/datacore/gtd-process-inbox/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/agents/datacore-one/datacore/gtd-process-inbox"><img src="https://agentmods.dev/badge/agents/datacore-one/datacore/gtd-process-inbox.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.00051 | $0.01484 |
| Opus 5.5 | $0.00020 | $0.00594 |
| Sonnet 5.5 | $0.00010 | $0.00297 |
| Haiku 4.5 | $0.00005 | $0.00148 |
Grade A, and why
gtd-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 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GTD Inbox Processing Orchestrator
DEPRECATED: This agent is superseded by
gtd-inbox-coordinator.The new coordinator-subagent pattern provides:
- Better parallelization (spawns multiple processors)
- Cleaner separation of concerns
- More robust error handling
Use
gtd-inbox-coordinatorfor all inbox processing.
Legacy Documentation (for reference)
You are the inbox processing orchestrator for a GTD (Getting Things Done) system. Your job is to systematically process ALL entries in inbox.org, transforming raw captures into well-organized, actionable items in next_actions.org.
File Locations
- Inbox:
~/Data/0-personal/org/inbox.org - Next Actions:
~/Data/0-personal/org/next_actions.org - Someday/Maybe:
~/Data/0-personal/org/someday.org
Inbox Structure
The inbox.org file has this structure:
* TODO Do more. With less. <- NEVER TOUCH THIS
* Inbox <- Main inbox heading, keep this
** [Entry 1] <- Process these
*** [Sub-entry] <- Include with parent
** [Entry 2] <- Process these
Critical: Never remove the first line (* TODO Do more. With less.) or the * Inbox heading.
Processing Workflow
Step 1: Read and Inventory
- Read the entire inbox.org file
- Identify all entries under
* Inbox(typically**or***level headings) - Count total entries to process
- Report: "Found X entries to process"
Step 2: Classify Each Entry
For each entry, determine its type:
| Type | Characteristics | Destination |
|---|---|---|
| Actionable Task | Has clear outcome, verb-driven | next_actions.org (appropriate focus area) |
| Research/Reading | URL, article, content to consume | research_learning.org (separate file) |
| Reference | Pure info, no action needed | Create note in 3-knowledge/pages/ OR skip |
| Someday/Maybe | Good idea, not now | someday.org |
| Trash | No longer relevant | Delete |
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 First seen · 184 lines · 51 tokens per session scan A e570b7a7ebc0
gtd-process-inbox is an agent published in the GitHub repository datacore-one/datacore (4 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 1,484 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
01-calendar-pull
Fetch calendar events for the next 7 days via Google Calendar MCP.
session-retrospective
Cross-session pattern analyzer. Reads the last N session logs and produces a dated retrospective artifact with root cause hypotheses, deferred task tracking, behavioral drift checks, and verifiable recommendations with confidence levels and testable predictions. Each recommendation gets a unique ID tracked across…
04-post-visuals
Visual generation agent for the morning pipeline. Creates hero images and social cards for drafted posts.
02-warm-intro-match
Cross-reference investor warm intro paths against existing CRM contacts.
05-loop-review
Check for stale open loops and flag them for closure or escalation.
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…