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/updategit 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/update)<a href="https://agentmods.dev/commands/wookiya1364/scv-claude-code/update"><img src="https://agentmods.dev/badge/commands/wookiya1364/scv-claude-code/update.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.00068 | $0.00917 |
| Opus 5 | $0.00034 | $0.00458 |
| Sonnet 5 | $0.00014 | $0.00183 |
| Haiku 4.5 | $0.00007 | $0.00092 |
Grade B, and why
update scanned grade B with 1 finding 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 3d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
1. `~/.claude/settings.json` (or project `.claude/settings.json` / `.claude/settings.local.json`) — `language` key. How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/scv:update
Update the installed SCV plugin to the latest release.
Claude Code's slash commands cannot self-update the host plugin directly — this command runs a version diagnostic and walks the user through the two built-in commands required: /plugin marketplace update <name> and /reload-plugins.
Language preference
Resolve the user's preferred language with this priority, then use it for status messages and questions:
~/.claude/settings.json(or project.claude/settings.json/.claude/settings.local.json) —languagekey.- Project
.env—SCV_LANG. - Auto-detect from the user's most recent message language.
- Default to English.
Technical identifiers (slash command names like /plugin marketplace update, plugin/marketplace names, version tags) stay as-is in every language.
Protocol
Step 1 — Run the diagnostic
"${CLAUDE_PLUGIN_ROOT}/scripts/update.sh"
Parse the output keys:
INSTALLED_VERSION:— current plugin.json versionMARKETPLACE_NAME:— marketplace.json root name (scv-claude-code)PLUGIN_NAME:— plugin.json name (scv)LATEST_VERSION:— latest GitHub release tag (gh CLI), or(unavailable — ...)with reasonUP_TO_DATE:—yes/no/unknown
Step 2 — Report + guide based on UP_TO_DATE
Branch by UP_TO_DATE value:
| Value | Action |
|---|---|
yes |
Report: "Already on latest (<INSTALLED_VERSION>). No action needed." Stop. |
no |
Report: "Installed <INSTALLED_VERSION> → latest <LATEST_VERSION>." Then proceed to Step 3 (guide commands). |
unknown |
Report the unavailability reason (from LATEST_VERSION: line). Then ask via AskUserQuestion whether to proceed with manual update commands anyway (Step 3) or stop. |
Step 3 — Guide the two built-in commands
Print to the user, in the resolved language:
To update, run these two commands in this Claude Code session:
/plugin marketplace update <MARKETPLACE_NAME> /reload-pluginsThe first refreshes the marketplace's local copy. The second activates the updated plugin without restarting Claude Code.
After both run, re-invoke
/scv:updateto verify the new version is detected.
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.
- 3d ago First seen · 84 lines · 68 tokens per session scan B a3121b0b6e96
update is a command published in the GitHub repository wookiya1364/scv-claude-code (7 stars, last pushed 6d ago), licensed MIT. It adds 68 tokens to every session and 917 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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).