handle

A command for taking a non-code operations task from planning through execution. It uses separate planning and execution steps for research, strategy, content, and specifications.

In plain words
What is it for?
Use it for research projects, strategic work, content creation, and specifications. It must not be used for code changes.
Why use it?
It gives non-code work a defined path from understanding the task to carrying out the approved plan and reviewing the result.

Command

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.

agentmods
npx agentmods add commands/odinmb/ops-workflow/handle
Clone the repo
git clone --depth 1 https://github.com/OdinMB/ops-workflow
Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 157 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00039 $0.00157
Opus 5 $0.00019 $0.00078
Sonnet 5 $0.00008 $0.00031
Haiku 4.5 $0.00004 $0.00016

Measured yesterday against content hash 8cf9e25492b9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

commands/handle.md · 18 lines

What it actually says

Handle

Follow this process for all non-trivial ops work.

1. Planning

Use the /plan skill. It handles research, plan file creation, clarification, and user presentation. Do NOT use EnterPlanMode — stay in the current permission mode throughout.

2. Execution

Use the /execute skill with the approved plan file. It handles execution, review, state updates, insight harvesting, and plan archiving.

Do not skip this step. If the conversation is ending and you haven't done this, do it now.

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. yesterday First seen · 18 lines · 39 tokens per session scan A 8cf9e25492b9

Subscribe to this mod's changes

handle is a command published in the GitHub repository OdinMB/ops-workflow (7 stars, last pushed 14d ago), licensed MIT. It adds 39 tokens to every session and 157 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-31.