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/outbox)<a href="https://agentmods.dev/commands/datacore-one/datacore/outbox"><img src="https://agentmods.dev/badge/commands/datacore-one/datacore/outbox/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/outbox"><img src="https://agentmods.dev/badge/commands/datacore-one/datacore/outbox.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.00020 | $0.01969 |
| Opus 5.5 | $0.00008 | $0.00788 |
| Sonnet 5.5 | $0.00004 | $0.00394 |
| Haiku 4.5 | $0.00002 | $0.00197 |
Grade A, and why
outbox 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/outbox Command
Command Context
When to Reference DIP-0017
Always reference when:
- Moving content to archive
- Processing
4-archive/folders - Setting up archive repos on nightshift server
- Determining routing destinations
Key decisions this DIP informs:
- Content leaving active workspace goes through
4-archive/ - Archive is permanent storage, no automatic retention cleanup
- Archive repos live on server (or local for local-only deployment)
- Preserve semantic path structure when archiving
Quick Reference
| Question | Answer |
|---|---|
| What is 4-archive? | The space's single exit folder (DIP-0017 as amended 2026-10-18) |
| Where do archived files go? | Server archive repos: [space]-archive/ |
| What about companions? | Always move together with source file |
| Is archive permanent? | Yes, no automatic cleanup |
| What DIPs govern this? | DIP-0017 (Outbox), DIP-0015 (Semantic Org) |
Agents This Command Invokes
| Agent | Purpose |
|---|---|
outbox-processor |
Routes content to destinations |
archive-indexer |
Updates search index after archiving |
Integration Points
- DIP-0017 - Outbox/archive specification
- DIP-0015 - Semantic organization, folder structure
- DIP-0011 - Nightshift integration for scheduled processing
Process the outbox queue and route content to destinations. Its queue is each space's 4-archive/, the single exit folder (there is no 4-outbox/). A non-dry run copies content to the archive repo and deletes the local copy: always dry-run first and get the owner's go.
Usage
/outbox # Process all spaces
/outbox [space] # Process specific space
/outbox --dry-run # Preview without moving
Workflow
Phase 1: Discovery
- Load configuration from
.datacore/settings.yaml:outbox.archive_location(server|local)outbox.server_host(server IP)outbox.archive_repos(repo paths)
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 Changed 06c53c59b55a
- 1mo ago First seen · 263 lines · 20 tokens per session scan A 6c2038d03d35
outbox is a command published in the GitHub repository datacore-one/datacore (4 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 1,969 once invoked, about $0.0001 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.
Other commands, from other repositories
linear-drain
Create the queued Linear projects and issues that shell scripts captured offline.
voice-refresh
Refresh the founder-voice DNA from new Granola meetings (interactive, MCP-backed). Pulls meetings since the last refresh, harvests Assaf-only speech, runs the Stage 2-3 orchestrator, and presents a founder-gated delta. Never auto-writes voice-dna.md.
decompose
Feature/story breakdown — consume a ready-for-decompose scope doc and produce a task graph in the issue tracker. Re-entrant; tracker-as-canonical with vault breadcrumb.
memory-sprint
Show current sprint state from StudioMeyer Memory.
draft-issue
Draft a GitHub issue based on a discussion or requirements in the current conversation.
close-task
Close the task: update tracking and optionally its GitHub issue.