Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add sivang/sivan-claude-plugins/plugin install vertex-ai-providerWrote 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/sivang/sivan-claude-plugins/vertex-stats)<a href="https://agentmods.dev/commands/sivang/sivan-claude-plugins/vertex-stats"><img src="https://agentmods.dev/badge/commands/sivang/sivan-claude-plugins/vertex-stats.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.1 | $0.00005 | $0.00211 |
| Opus 5 | $0.00003 | $0.00105 |
| Sonnet 5 | $0.00001 | $0.00042 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade B, and why
vertex-stats 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 5d 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.
- Current state: !`cat ~/.claude/vertex-provider/state.json 2>/dev/null || echo '{"active":false}'` What it actually says
Context
- Current state: !
cat ~/.claude/vertex-provider/state.json 2>/dev/null || echo '{"active":false}' - Arguments: $ARGUMENTS
Your Task
Show usage statistics based on arguments:
No arguments (default to current session)
node "${CLAUDE_PLUGIN_ROOT}/lib/cli/stats.js"
With period (today, week, month)
node "${CLAUDE_PLUGIN_ROOT}/lib/cli/stats.js" today
node "${CLAUDE_PLUGIN_ROOT}/lib/cli/stats.js" week
node "${CLAUDE_PLUGIN_ROOT}/lib/cli/stats.js" month
With --graph flag
node "${CLAUDE_PLUGIN_ROOT}/lib/cli/stats.js" week --graph
Run the appropriate command based on the user's arguments.
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.
- 5d ago First seen · 34 lines · 5 tokens per session scan B 6397b29efddb
vertex-stats is a command published in the GitHub repository sivang/sivan-claude-plugins (1 stars, last pushed 7mo ago), licensed MIT. It adds 5 tokens to every session and 211 once invoked, about $0.0000 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
validate
Mechanically validate the sonu plugin repo before a PR — manifest sync, YAML frontmatter, shell-fence syntax, named-source and AI-attribution scans, cross-reference integrity, skill reachability. Only meaningful inside the claude-plugins repo; in any other repo, say so and stop.
build
Sequence decide → build → hand back for any feature or fix. Triage the change, run design-tree in plan mode (with you as the approval gate — skipped when /sonu:factory routes a ticket whose spec you already approved), build test-first under code-standards, then surface the riskiest parts before handing back to…
release
Prepare a release of the sonu plugin — decide the semver bump, sync the version and plugin description across all five homes, run /validate, then hand to /sonu:ship. Only meaningful inside the claude-plugins repo; in any other repo, say so and stop.
audit
Full quality audit — runs security scan, performance check, and test coverage analysis in sequence and produces a combined report.
check
Run static analysis on the Java project — detects configured tools (Checkstyle, SpotBugs, PMD) and reports findings.
routes
List all REST endpoints in the Spring Boot project — scans controllers and prints a route table.