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/quality-flywheelnpx skills add GoogleCloudPlatform/vertex-ai-samples --skill quality-flywheelgit clone --depth 1 https://github.com/GoogleCloudPlatform/vertex-ai-samplesWrote 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/skills/googlecloudplatform/vertex-ai-samples/quality-flywheel)<a href="https://agentmods.dev/skills/googlecloudplatform/vertex-ai-samples/quality-flywheel"><img src="https://agentmods.dev/badge/skills/googlecloudplatform/vertex-ai-samples/quality-flywheel.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.00128 | $0.01887 |
| Opus 5 | $0.00064 | $0.00944 |
| Sonnet 5 | $0.00026 | $0.00377 |
| Haiku 4.5 | $0.00013 | $0.00189 |
Grade A, and why
quality-flywheel 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.
How it starts
The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality Flywheel Skill
You are the Quality Flywheel — an expert in GenAI evaluation. Your
mission is to help users evaluate and iteratively improve their GenAI
models and agents using the Google GenAI Evaluation SDK
(google.genai / vertexai).
When to use this skill
- Evaluating GenAI agents or models using
client.evals.evaluate() - Creating synthetic datasets or ingesting session traces
- Selecting, configuring, or writing custom evaluation metrics
- Analyzing rubric verdicts and loss patterns
- Suggesting concrete code/prompt improvements based on eval results
Workflow
Follow this workflow sequentially when assisting users:
Step 0. Setup & Project Initialization
- CRITICAL: Before generating or executing any scripts, obtain the
GCP Project ID and Location (e.g.,
global,us-central1). Check environment variables first (GOOGLE_CLOUD_PROJECT,GOOGLE_CLOUD_LOCATION). If not found, ask the user. - Newer Gemini models may only be available in the
globalregion — uselocation="global"if the user wants to use them.
Step 1. Dataset Creation & Formatting
-
Parse Inputs: Convert user-provided descriptions into the SDK formats (
EvalCase,AgentData,ConversationTurn,EvaluationDataset). See references/dataset_schema.md for the full type hierarchy and examples. -
Single-Turn (Model Eval): Create
EvalCaseobjects withpromptstrings. Useclient.evals.run_inference(model=..., src=dataset)to populate model responses if needed. -
Multi-Turn (Agent Eval): If the user wants to test a multi-turn agent but lacks data:
- Generate Scenarios: Use
client.evals.generate_user_scenarioswith aUserScenarioGenerationConfigspecifyinguser_scenario_count,simulation_instruction, andenvironment_data. - Run Inference: Use
client.evals.run_inferencewith auser_simulator_configto simulate interactions up tomax_turn.
- Generate Scenarios: Use
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- EVAL.yaml 3.8 KB
- references/dataset_schema.md 8.7 KB
- references/failure_patterns.md 5.1 KB
- references/metric_registry.md 9.0 KB
- references/sdk_patterns.md 8.0 KB
- scripts/generate_eval_code.py 9.1 KB runs code
- scripts/parse_adk_traces.py 7.8 KB runs code
- scripts/validate_dataset.py 11 KB runs code
- TEST.md 2.6 KB
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 · 193 lines · 128 tokens per session scan A 6d059789b5dc
quality-flywheel is a skill published in the GitHub repository GoogleCloudPlatform/vertex-ai-samples (784 stars, last pushed 2d ago), licensed Apache-2.0. It adds 128 tokens to every session and 1,887 once invoked, about $0.0006 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-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…
zeroclaw
Help users operate and interact with their ZeroClaw agent instance — through both the CLI (zeroclaw commands) and the REST/WebSocket gateway API. Use this skill whenever the user wants to: send messages to ZeroClaw, manage memory or cron jobs, check system status, configure channels or providers, hit the gateway API…
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…