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 skills add hamzabellouch/agent-skills --skill agent-platform-migrate-from-ai-studiogit clone --depth 1 https://github.com/hamzabellouch/agent-skillsWrote 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/hamzabellouch/agent-skills/agent-platform-migrate-from-ai-studio)<a href="https://agentmods.dev/skills/hamzabellouch/agent-skills/agent-platform-migrate-from-ai-studio"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/agent-platform-migrate-from-ai-studio/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/skills/hamzabellouch/agent-skills/agent-platform-migrate-from-ai-studio"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/agent-platform-migrate-from-ai-studio.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.00064 | $0.03079 |
| Opus 5 | $0.00032 | $0.01540 |
| Sonnet 5 | $0.00013 | $0.00616 |
| Haiku 4.5 | $0.00006 | $0.00308 |
Grade A, and why
agent-platform-migrate-from-ai-studio 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 11d 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.
This is a copy
100% identical to agent-platform-migrate-from-ai-studio — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 363 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrating from Gemini API in AI Studio to Agent Platform
Use this skill when you need to transition an application from the
developer-centric Google AI Studio ecosystem
(generativelanguage.googleapis.com) to the enterprise-grade Google Cloud Agent
Platform (aiplatform.googleapis.com).
When to Invoke This Skill
- You want to migrate an application from Google AI Studio to Agent Platform (formerly Vertex AI).
- You have Google Cloud credits (e.g., the $300 Welcome Free Trial) that you want to apply toward Gemini API inferencing costs.
- You need to unify your inferencing pipelines, IAM permissions, telemetry, and billing with existing Google Cloud infrastructure (Compute Engine, Cloud SQL, BigQuery).
- You are deploying open-source orchestration engines (like OpenClaw or ADK agents) on Google Cloud VMs, and want the entire system to run under a unified Google Cloud billing structure.
Gemini API Comparison
| Feature / Control | Google AI Studio (Gemini Developer API) | Agent Platform (Enterprise Gemini API) |
|---|---|---|
| API Endpoint | generativelanguage.googleapis.com |
aiplatform.googleapis.com |
| Target Audience | Developers, startups, students, researchers building production apps. | Enterprise production, MLOps engineers |
| GCP Credit Support | No (GCP credits/Free Trial cannot be applied) | Yes (Fully covered by Welcome or custom credits) |
| Data Privacy | Data may be reviewed to improve Google products | Prompts/responses are never used for training |
| Security & IAM | API key, OAuth | Google Cloud IAM (Service Accounts, OAuth 2.0, VPC-SC) |
| Compliance & SLAs | None (Best-effort availability) | 24/7 Enterprise Support, SLAs, HIPAA, SOC2 |
| Throughput Options | Shared / Rate-limited | Pay-as-you-go OR Provisioned Throughput |
| MLOps Ecosystem | Basic prompt management | Model Registry, Model Monitoring, Pipeline Evaluation |
| Inferencing Scope | Global endpoints only | Both Global and strict Regional endpoints |
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.
- 11d ago First seen · 363 lines · 64 tokens per session scan E 66dc58c04439
agent-platform-migrate-from-ai-studio is a skill published in the GitHub repository hamzabellouch/agent-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 3,079 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to agent-platform-migrate-from-ai-studio, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
spec-create
Create a structured feature specification with self-contained task files organized into parallel execution batches. Use this skill when the user says "create a spec", "plan this feature", "write up an implementation plan", "break this into tasks", or after any planning conversation where the user wants to capture…
spec-implement
Orchestrate parallel implementation of a feature specification by dispatching coder agents batch-by-batch with code review gates between batches. Use this skill when the user says "implement this feature", "start implementing", "run the spec", "execute the plan", "continue implementing", or wants to begin coding a…
spec-ship
Push the current branch to GitHub and create a pull request. Use this skill when the user says "ship it", "ship this", "push to github", "create a pr", "open a pull request", "send for review", "get this reviewed", or wants to push their work and open a PR. Also use when the user says "/spec-ship" (or their host's…
spec-checkpoint
Create a comprehensive checkpoint commit with detailed analysis of all changes. Use this skill when the user says "checkpoint", "commit everything", "save my progress", "create a commit", or wants to stage and commit all current changes with a well-crafted message. Also use when the user says "/spec-checkpoint" (or…
generative-seo
Run an evidence-based SEO + GEO (Generative Engine Optimization) program for ANY website or product codebase — auditing technical SEO, writing or retrofitting content so it gets cited by ChatGPT/Perplexity/AI Overviews, tracking AI-citation visibility, refreshing competitor research, and drafting distribution posts.…
spec-verify
Verify a completed feature spec by driving the real running app — not just lint/typecheck/build — and checking off every acceptance criterion from its specs/{feature}/ folder one by one. Use this after /spec-implement finishes a spec, when the user says "test this end to end", "verify this feature actually works"…