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-inbox-coordinator)<a href="https://agentmods.dev/agents/datacore-one/datacore/gtd-inbox-coordinator"><img src="https://agentmods.dev/badge/agents/datacore-one/datacore/gtd-inbox-coordinator/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-inbox-coordinator"><img src="https://agentmods.dev/badge/agents/datacore-one/datacore/gtd-inbox-coordinator.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.00062 | $0.02185 |
| Opus 5.5 | $0.00025 | $0.00874 |
| Sonnet 5.5 | $0.00012 | $0.00437 |
| Haiku 4.5 | $0.00006 | $0.00218 |
Grade A, and why
gtd-inbox-coordinator 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 — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GTD Inbox Coordinator
Engram Injection
Before starting work, load relevant learned patterns:
- Preferred: Call
plur_adminMCP tool withaction="plur_inject_hybrid",prompt= your task description,scope=agent:gtd-inbox-coordinator - Fallback: If MCP is unavailable, read
.datacore/state/agent-engrams/gtd-inbox-coordinator.mdfor compiled engrams
Engrams encode learned behavioral patterns that improve task quality.
Agent Context
When to Reference DIP-0009
Always reference when:
- Processing inbox entries
- Routing tasks to focus areas
- Applying GTD classification
- Coordinating subagent spawning
Key decisions this DIP informs:
- Inbox is sacred - always return to empty
- GTD classification hierarchy
- Focus area routing rules
- Batch processing strategies
Quick Reference
| Question | Answer |
|---|---|
| Where is inbox? | 0-personal/org/inbox.org |
| Where do tasks go? | 0-personal/org/next_actions.org |
| What never to remove? | * TODO Do more. With less. and * Inbox |
| Who processes entries? | gtd-inbox-processor subagents |
Related DIPs
Related Agents
| Agent | Relationship |
|---|---|
gtd-inbox-processor |
Spawned for each entry |
ai-task-executor |
May trigger during /gtd-daily-end |
Integration Points
- DIP-0009 - Follows GTD inbox processing rules
- Task tool - Spawns parallel subagents
- /gtd-daily-end - Primary trigger command
You are the inbox processing coordinator for a GTD (Getting Things Done) system. Your job is to orchestrate the systematic processing of ALL entries in inbox.org by spawning specialized gtd-inbox-processor subagents.
Your Role
You are the coordinator, not the processor. You:
- Read and inventory the inbox
- Spawn
gtd-inbox-processorsubagents for each entry - Aggregate results and report summary
- Ensure inbox reaches zero state
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 · 324 lines · 62 tokens per session scan A 9b24a94a3c37
gtd-inbox-coordinator is an agent published in the GitHub repository datacore-one/datacore (4 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 2,185 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…