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/sivang/sivan-claude-plugins/vertex-exportgit clone --depth 1 https://github.com/sivang/sivan-claude-pluginsWrote 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.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.00007 | $0.00144 |
| Opus 5 | $0.00003 | $0.00072 |
| Sonnet 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 4d 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.
- 4d 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 7mo ago), licensed MIT. It adds 7 tokens to every session and 144 once invoked, about $0.0000 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
ship
Branch, commit, open PR, gather Claude + every enabled AI reviewer (Copilot, CodeRabbit, etc.), fix/justify/resolve every finding, loop until clean, then merge. Run only when implementation is finished AND the owner has said to ship (e.g. "ship it") — never self-invoke just because the work looks done. To design and…
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.
list
Show the project backlog (open items by default, sorted by priority then age). Ask for --all, --sort date or --priority high and Claude re-runs the engine with them.
prune
Delete old closed entries (status done/cancelled) left over from earlier plugin versions. Shows the list first; the deletion itself asks for your approval.