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/EZotoff/ez-omo-configWrote 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/ezotoff/ez-omo-config/handoff)<a href="https://agentmods.dev/commands/ezotoff/ez-omo-config/handoff"><img src="https://agentmods.dev/badge/commands/ezotoff/ez-omo-config/handoff/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/ezotoff/ez-omo-config/handoff"><img src="https://agentmods.dev/badge/commands/ezotoff/ez-omo-config/handoff.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.00015 | $0.00282 |
| Opus 5.5 | $0.00006 | $0.00113 |
| Sonnet 5.5 | $0.00003 | $0.00056 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
handoff 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.
What it actually says
Emit a handoff artifact for the current session using the handoff-relay skill procedure (load it via the skill tool if available; otherwise apply the procedure below inline).
Emit at a stable boundary only. If the current moment is mid-task, say so and ask whether to checkpoint-and-emit anyway.
Write the artifact to .builder-kit/audit/handoff-<slug>-<YYYY-MM-DD>.md (slug defaults to a 2-4 word kebab-case summary of the session's mission) with sections: Mission / Entry artifacts (read these first) / State (done with commit refs, in flight with exact coordinates, gotchas) / Next steps (numbered, each with a verifiable done-condition) / Prohibitions. Header records: emitted timestamp, source session ID, source head (sha + branch + clean/dirty), and which previous handoff this supersedes.
Rules: cite commits and session IDs exactly; a dirty tree is a warning label in the header, not a blocker; if a previous handoff file exists for this thread, mark it superseded.
Reply with the artifact path and a 3-line summary. Do not continue working on anything else after emitting — the next move (usually /resume-from in a fresh session) belongs to the operator.
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 · 14 lines · 15 tokens per session scan A 52aed08be4de
handoff is a command published in the GitHub repository EZotoff/ez-omo-config (6 stars, last pushed 7d ago), licensed MIT. It adds 15 tokens to every session and 282 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-06.
Other commands, from other repositories
icode
An end-to-end coding workflow invoked with the /icode command and several task-specific options. It routes work through steps such as planning, coding, review, verification, documentation, and worktree management.
capture
Run stackmemory capture to commit current work and generate a handoff prompt for the next session.
commit
When you receive this command, do the following.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
Stage, commit, and optionally ship further. Pass an escalation token (push, pr, merge, squash, squash merge) to skip the prompt. With no token, commits then asks how far to ship. Delegates message format to the atomic-git-discipline skill.
hatch3r-pr-resolve
Read open PR comments, evaluate each against current code via the rigor contract, implement accepted findings, reply inline. Multi-platform.