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.
git 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/plugins/sivang/sivan-claude-plugins/vertex-ai-provider)<a href="https://agentmods.dev/plugins/sivang/sivan-claude-plugins/vertex-ai-provider"><img src="https://agentmods.dev/badge/plugins/sivang/sivan-claude-plugins/vertex-ai-provider.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
vertex-ai-provider 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 6d 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
{
"name": "vertex-ai-provider",
"version": "1.0.0",
"description": "Use Claude models via Google Vertex AI with real-time token tracking and cost analytics",
"author": {
"name": "Sivan Grünberg",
"email": "[email protected]",
"url": "https://vitakka.co"
},
"homepage": "https://github.com/sivang/sivan-claude-plugins",
"repository": "https://github.com/sivang/sivan-claude-plugins",
"license": "MIT",
"keywords": ["vertex-ai", "gcp", "google-cloud", "token-tracking", "cost-analytics", "claude"]
}
What it installs
The manifest is a name and a version. 5 commands travel with it, and installing the plugin installs all of them — 36 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 6d ago First seen · 15 lines scan A a7096e6b850d
vertex-ai-provider is a plugin published in the GitHub repository sivang/sivan-claude-plugins (1 stars, last pushed 7mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
odin-formal
ODIN workflows for formal methods: model checking, SMT solving, deductive verification, and proof assistants.
prompt-pilot
Turns rough, vague prompts into precise, context-enriched prompts. Explores the current codebase read-only, weaves real file paths and symbols into the rewritten prompt, and never implements the task itself.
rayapatiranjithai-plugins marketplace
Prompt-engineering tools for Claude Code — live prompt-quality coaching scored against documented standards.
prompt-analyzer
Analyzes and coaches how the user writes prompts, measured against Anthropic's prompt-engineering standards, with persistent per-session statistics.
petprompt
A cute terminal pet that refines your rough prompts using your current session's context, memory, and model. No API key.
prompt-coach
Dual-axis coaching on every Claude Code prompt: improves prompt quality and target-language expression.