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/yempik-ai/cowork-osWrote 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/yempik-ai/cowork-os/process-inbox)<a href="https://agentmods.dev/commands/yempik-ai/cowork-os/process-inbox"><img src="https://agentmods.dev/badge/commands/yempik-ai/cowork-os/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/commands/yempik-ai/cowork-os/process-inbox"><img src="https://agentmods.dev/badge/commands/yempik-ai/cowork-os/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.00048 | $0.00289 |
| Opus 5 | $0.00024 | $0.00144 |
| Sonnet 5 | $0.00010 | $0.00058 |
| Haiku 4.5 | $0.00005 | $0.00029 |
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 10d 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.
What it actually says
/cowork-os:process-inbox
The user has unsorted material. Organize it into the workspace.
- Read everything in
_inbox/(and any links or notes the user pasted). If_inbox/does not exist, ask them to drop material there or paste it. - Extract the facts. Route each to the most specific file:
- company, market, status:
context/overview.md - value proposition, messages, differentiation:
context/positioning.md - offers, pricing, use cases:
context/services.md - voice:
context/tone_of_voice.md - campaigns, analytics:
marketing/ - site, copy, SEO:
website/ - decisions and assumptions:
decisions/ - owned products:
products/
- company, market, status:
- Separate facts, assumptions, and open questions. Never invent. Missing facts go to
decisions/open_questions.md. - Be non-destructive: keep originals, ask before moving or deleting.
- Report a short table: source, filed-in, confidence.
End with a Memory Update.
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.
- 10d ago First seen · 24 lines · 48 tokens per session scan A 5ecb9ed72153
process-inbox is a command published in the GitHub repository yempik-ai/cowork-os (70 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 289 once invoked, about $0.0002 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-08-30.
Other commands, from other repositories
setup
Set up this folder as a knowledge vault — adapts to an empty folder or an existing vault.
ingest
Turn material into notes at the right altitude — a quick capture, a small collection, or a full build.
log
Append a quick timestamped entry to today's daily log.
flow-nexus-user-tools
User management, storage, and system utilities.
triage
Triage Linear issue with comprehensive analysis.
todo.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.