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/workspacegit 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/workspace)<a href="https://agentmods.dev/commands/wookiya1364/scv-claude-code/workspace"><img src="https://agentmods.dev/badge/commands/wookiya1364/scv-claude-code/workspace.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.00083 | $0.01336 |
| Opus 5 | $0.00042 | $0.00668 |
| Sonnet 5 | $0.00017 | $0.00267 |
| Haiku 4.5 | $0.00008 | $0.00134 |
Grade A, and why
workspace 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/scv:workspace
Interactive setup for nested multi-repo SCV. Ask a couple of simple questions and
this runs the right thing under the hood — no need to remember
sync --join --id --role … or hydrate --root.
Language preference
Resolve the user's preferred language from scv/scv_settings.json SCV_LANG, then the latest
user message, then English. Keep technical identifiers (repo_id, root,
skill invocations, paths) as-is.
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?"
This governs everything the user reads: answers, questions, plans, progress reports, summaries, and explanations of what went wrong.
Protocol
Step 1 — detect current state
bash "${CLAUDE_PLUGIN_ROOT}/scripts/workspace-helper.sh" info
Parse MODE: → one of NOT_HYDRATED | SINGLE | ROOT | CHILD.
NOT_HYDRATED→ tell the user to run/scv:helpfirst to hydrate, then stop.
Step 2 — branch by MODE
MODE = SINGLE → offer to set up
Ask the user for confirmation "이 레포를 워크스페이스에서 어떻게 둘까요?":
- 합류 (자식) — 이 레포가 FE/BE/AI 중 하나로 기존 우산에 들어감
- 우산 만들기 (루트) — 이 레포가 모두를 아우르는 최상위
- 그냥 단일로 둔다 — 변경 없음
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 033dc40e5c0c
- 4d ago First seen · 107 lines · 83 tokens per session scan A 6ab456afb6a9
workspace is a command published in the GitHub repository wookiya1364/scv-claude-code (7 stars, last pushed today), licensed MIT. It adds 83 tokens to every session and 1,336 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-discord
Post a Discord message via Caspian (channel snowflake id).
caspian-inbox
List Caspian inbox messages (email + configured channels).