process

process is a command for Claude Code from revaya-ai/revaya-aios-workspace-template. It costs 0 tokens per session (1,033 once invoked), scanned A, original, MIT.

A command for processing a Getting Things Done inbox, a list of unorganized captured tasks and notes, until every item has a destination.

In plain words
What is it for?
Use it to review the inbox, check related GTD lists, and decide what to do with each captured item.
Why use it?
It prevents inbox items from remaining undecided by sorting each one into an action, project, waiting list, someday list, reference, or trash.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions Claude Code.

Good fit Use it to review the inbox, check related GTD lists, and decide what to do with each captured item.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/revaya-ai/revaya-aios-workspace-template/process
Install

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.

Clone the repo
git clone --depth 1 https://github.com/revaya-ai/revaya-aios-workspace-template

Made for: Claude Code.

Wrote 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.

agentmods badge for process

README.md
[![agentmods](https://agentmods.dev/badge/commands/revaya-ai/revaya-aios-workspace-template/process/github.svg)](https://agentmods.dev/commands/revaya-ai/revaya-aios-workspace-template/process)
Your own site
<a href="https://agentmods.dev/commands/revaya-ai/revaya-aios-workspace-template/process"><img src="https://agentmods.dev/badge/commands/revaya-ai/revaya-aios-workspace-template/process/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.

agentmods 80×15 button for process

Your own site · 80×15
<a href="https://agentmods.dev/commands/revaya-ai/revaya-aios-workspace-template/process"><img src="https://agentmods.dev/badge/commands/revaya-ai/revaya-aios-workspace-template/process.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,033 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01033
Opus 5 $0.00000 $0.00517
Sonnet 5 $0.00000 $0.00207
Haiku 4.5 $0.00000 $0.00103

Measured 9d ago against content hash 7c388718a074, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

process 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 9d 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.

.claude/commands/process.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Process

Process the GTD inbox to zero. Walks through each captured item using the GTD decision tree — routes to projects, next-actions, waiting-for, someday-maybe, or trash.


Instructions

You are helping the user process their GTD inbox to zero. Every item gets a decision — nothing stays in the inbox.


Step 1: Load Inbox

  1. Read gtd/inbox.md
  2. If inbox is empty, report: "Inbox is at zero — nothing to process." and stop.
  3. Count items and report: "You have [N] items in the inbox. Let's process them."

Also read for context (so you can route items to the right places):

  • gtd/projects.md — existing projects
  • gtd/next-actions.md — existing actions
  • gtd/waiting-for.md — existing delegated items
  • gtd/someday-maybe.md — existing backlog

Step 2: Process Each Item

Present items one at a time (or in small batches if clearly related). For each item, walk through the GTD decision tree:

Decision Tree

"Is this actionable?"
  |
  NO --> Ask:
  |   "Trash it?" --> Delete from inbox
  |   "Someday/Maybe?" --> Move to gtd/someday-maybe.md (choose category)
  |   "Reference?" --> Note where to file it
  |
  YES --> Ask:
      "Does this connect to the One Objective or the current Bottleneck?" (soft check — see OOBG below)
      |
      "Is this a multi-step outcome?" --> YES: Add to gtd/projects.md
      "What's the very next physical action?"
      |
      Takes <2 minutes? --> "Do it now."
      |
      Someone else should do it?
      |   YES --> Add to gtd/waiting-for.md (who, what, date)
      |
      I should do it, >2 min
          Has a specific date/time? --> Calendar item
          As soon as I can? --> Add to gtd/next-actions.md (choose context)

OOBG Alignment Check (Soft — Habit Building)

For actionable items, ask one question: "Does this connect to the One Objective or the current Bottleneck?"

This is not a hard gate — not everything has to directly address the Bottleneck. But it's a signal:

  • If yes: route normally, flag as high priority if it's bottleneck-breaking
  • If no and it's required work: route normally, add [maintenance] note
  • If no and it's discretionary: consider "Is now the right time for this, or does it belong in Someday/Maybe?"

Read the full file on GitHub · 112 lines

Changes

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.

  1. 9d ago First seen · 112 lines · 0 tokens per session scan A 7c388718a074

Subscribe to this mod's changes

process is a command published in the GitHub repository revaya-ai/revaya-aios-workspace-template (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,033 tokens. 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.