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 skills/googlecloudplatform/vertex-ai-samples/gemininpx skills add GoogleCloudPlatform/vertex-ai-samples --skill geminigit clone --depth 1 https://github.com/GoogleCloudPlatform/vertex-ai-samplesWhat 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.00000 | $0.01640 |
| Opus 5 | $0.00000 | $0.00820 |
| Sonnet 5 | $0.00000 | $0.00328 |
| Haiku 4.5 | $0.00000 | $0.00164 |
Grade A, and why
gemini 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: vertex-tuning-gemini description: > Vertex AI Gemini Model Tuning. Use when you need to fine-tune Gemini models using Vertex AI's infrastructure.
Vertex AI Gemini Model Tuning
Overview
This skill provides procedural knowledge for fine-tuning Gemini Large Language Models using Vertex AI's tuning service. It covers the entire lifecycle from environment setup and data preparation to job configuration, monitoring, and deployment.
Workflow Decision Tree
-
Environment Check: Has the environment (Auth, APIs, IAM, Venv) been initialized?
- No → Go to Phase 0: Environment & IAM Setup.
- Yes → Proceed.
-
Dataset Status: Is the dataset ready in JSONL format and uploaded to GCS?
- No → Go to Phase 1: Dataset Preparation & Upload.
- Yes → Proceed.
-
Configuration: Have the target Gemini model and hyperparameters been decided?
- No → Go to Phase 2: Model Configuration & Recommendation.
- Yes → Proceed.
-
Job Status: Has the tuning job been submitted?
- No → Go to Phase 3: Tuning Job Execution.
- Yes → Proceed.
-
Job Completion: Is the tuning job complete?
- No → Go to Phase 4: Monitoring.
- Yes → Proceed.
-
Deployment: Has the tuned model been deployed (if required)?
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.
- 2d ago First seen · 208 lines · 0 tokens per session scan A 1769e8b6e60e
gemini is a skill published in the GitHub repository GoogleCloudPlatform/vertex-ai-samples (780 stars, last pushed 7d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,640 tokens. 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-30.
Other skills, from other repositories
retro-marimo-pair
Session retrospective for improving marimo-pair and marimo.codemode. Use when the user wants to analyze friction from a pairing session, identify what went wrong, and brainstorm improvements to the skill docs or the underlying API. Trigger on: "retro", "what went wrong", "improve the skill", "session review"…
marimo-pair
Drive a live marimo notebook as a workspace: run Python in the same kernel the user does, inspect live notebook state, and commit durable notebook changes. Use when the user wants to start a marimo notebook or pair on an active marimo session.
review-prs
Review a GitHub pull request in the googleapis/mcp-toolbox repo against the team's reviewer checklist: PR title/description conventions, linked issue, logic errors and unhandled edge cases, breaking changes, test coverage, docs updates, security (input handling), and new dependencies. Use whenever a maintainer asks…
stale-sweep
Sweep the googleapis/mcp-toolbox repo for issues and PRs with no real activity in N days (default 60), sort each by whose silence it is (the author's, ours, or nobody's), and draft the nudge or close comment. Use whenever a maintainer asks for a stale sweep, backlog cleanup, or an SLO check, e.g. "stale sweep", "find…
triage-issues
Triage GitHub issues in the googleapis/mcp-toolbox repo: propose the correct labels (type / priority / product / status), check for duplicates, verify a bug has enough info to act on, and draft a triage comment. Use whenever a maintainer asks you to triage, label, categorize, prioritize, or "look at" an issue (or a…
github-issue-triage
Issue triage and lifecycle management agent for ZeroClaw. Use this skill whenever the user wants to: triage open issues, close stale/duplicate/fixed issues, apply labels, run a backlog sweep, enforce the current issue stale policy, or handle a specific issue. Trigger on: 'triage issues', 'issue triage', 'sweep…