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.
npx agentmods add commands/wookiya1364/scv-claude-code/handoffgit clone --depth 1 https://github.com/wookiya1364/scv-claude-codeWrote 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/wookiya1364/scv-claude-code/handoff)<a href="https://agentmods.dev/commands/wookiya1364/scv-claude-code/handoff"><img src="https://agentmods.dev/badge/commands/wookiya1364/scv-claude-code/handoff.svg" alt="Measured on agentmods" 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 | $0.00078 | $0.01749 |
| Opus 5 | $0.00039 | $0.00874 |
| Sonnet 5 | $0.00016 | $0.00350 |
| Haiku 4.5 | $0.00008 | $0.00175 |
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 today.
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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/scv:handoff
Producer side of the nested multi-repo loop. Use it AFTER you (in this child repo)
have made or planned a change that requires corresponding development in another
repo (e.g. FE shipped a button that needs a new BE endpoint). It records the
explicit decision + the why and propagates them to the shared workspace
root scv repo, so the other repo sees it on git pull (/scv:status).
This is an explicit, human/Claude Code-judged declaration — SCV never infers cross-repo need from a code diff.
Mode
Only meaningful when this repo is a workspace CHILD or ROOT (it has an
SCV:WORKSPACE block with a root: set — see /scv:sync --join). In a plain
single repo it is a no-op (prints a notice and exits). Run nothing manually to
check — the script resolves the mode itself.
Language preference
Resolve the user's preferred language from scv/scv_settings.json SCV_LANG, then the latest
user message, then English. Use it for all user-facing prose. Keep technical
identifiers as-is (repo_id, handoff_id, skill invocations, paths).
Plain language first
Skip this section only when scv/scv_settings.json sets SCV_PLAIN_LANGUAGE=off
(absent or any other value = on).
Answer shape — every time you explain something to the user:
- First, 1–2 sentences. Lead with what the user gets.
The cap is 2 unless
scv/scv_settings.jsonsetsSCV_PLAIN_MAX_SENTENCES=<n>(a positive integer) — then up to n. - Then one example — from the user's situation, or an everyday comparison.
- No code values before the user asks: file paths, variable names, version numbers, setting values. Use the plain name instead ("the settings file", "last week's plan").
- Detail comes after, and only when wanted. Offer it in one line.
Identifiers the user needs to act on — the next command to run, a file that was created — stay exact, after the plain summary.
Bad: "The block landed in scv_settings.example.json:154-161 and the stamp advanced
2.1.0 → 2.2.0."
Good: "Your settings example file is up to date. For example, the new 'effort'
setting now shows there. Want the exact lines?"
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.
- today Changed · -1 lines 034bdbb8eb79
- 5d ago First seen · 128 lines · 78 tokens per session scan A dcfaaa9a82fc
handoff is a command published in the GitHub repository wookiya1364/scv-claude-code (7 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 1,749 once invoked, about $0.0004 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.
Other commands, from other repositories
caspian-email
Send or reply via Caspian email (ask thread vs new).
caspian-connect-email
Connect Caspian email (sandbox key or dashboard paste) and enable email in caspian.json.
caspian-connect-discord
Connect Caspian Discord and enable discord in caspian.json.
caspian-connect-telegram
Connect Caspian Telegram and enable telegram in caspian.json.
caspian-inbox
List Caspian inbox messages (email + configured channels).
caspian-telegram
Send a Telegram message via Caspian (@username).