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-export)<a href="https://agentmods.dev/commands/sivang/sivan-claude-plugins/vertex-export"><img src="https://agentmods.dev/badge/commands/sivang/sivan-claude-plugins/vertex-export/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/sivang/sivan-claude-plugins/vertex-export"><img src="https://agentmods.dev/badge/commands/sivang/sivan-claude-plugins/vertex-export.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.00007 | $0.00144 |
| Opus 5.5 | $0.00003 | $0.00058 |
| Sonnet 5.5 | $0.00001 | $0.00029 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
vertex-export 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
Context
- Arguments: $ARGUMENTS
- Export directory: ~/.claude/vertex-provider/exports/
Your Task
Export usage data to JSON:
Default (all data)
node "${CLAUDE_PLUGIN_ROOT}/lib/cli/export.js"
With date range
node "${CLAUDE_PLUGIN_ROOT}/lib/cli/export.js" --from 2025-01-01 --to 2025-01-25
Tell the user the full path to the exported file.
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 · 27 lines · 7 tokens per session scan A f37f4e435a16
vertex-export is a command published in the GitHub repository sivang/sivan-claude-plugins (1 stars, last pushed 9mo ago), licensed MIT. It adds 7 tokens to every session and 144 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
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…
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.
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.
routes
List all REST endpoints in the Spring Boot project — scans controllers and prints a route table.
run
Start the Spring Boot application locally — checks prerequisites, then runs the app and reports startup status.