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 jpantsjoha/ai-native-developer-experience --skill gcp-expertgit clone --depth 1 https://github.com/jpantsjoha/ai-native-developer-experienceWrote 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/jpantsjoha/ai-native-developer-experience/gcp-expert)<a href="https://agentmods.dev/skills/jpantsjoha/ai-native-developer-experience/gcp-expert"><img src="https://agentmods.dev/badge/skills/jpantsjoha/ai-native-developer-experience/gcp-expert.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.1 | $0.00059 | $0.01141 |
| Opus 5 | $0.00030 | $0.00571 |
| Sonnet 5 | $0.00012 | $0.00228 |
| Haiku 4.5 | $0.00006 | $0.00114 |
Grade A, and why
gcp-expert 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 8d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GCP Expert
Gemini Enterprise is the governed execution foundation — identity, tenancy, and compliance are the design constraints, not context window size.
This skill enforces the discipline that makes GCP workloads production-safe: identity, data boundaries, cost controls, and regional residency. It is not a GCP feature tour — it is a checklist of the things that cause incidents and compliance failures when skipped.
When to use
- Designing any GCP infrastructure (new or modified)
- Before deploying agents or LLM workloads to GCP
- When reviewing a Terraform plan or architecture diagram for a GCP workload
- When a system touches multiple tenants, regulated data, or crosses regional boundaries
Procedure
-
Identity and IAM — verify least-privilege for every service account and human role:
- Service accounts have only the roles required for their specific function. No
roles/editororroles/owneron service accounts. - Workload Identity Federation preferred over service account keys for GKE / Cloud Run workloads.
- Conditional Access and IAM conditions applied where granular, time-bound, or context-aware control is required.
- Service accounts have only the roles required for their specific function. No
-
Governance and resource hierarchy — confirm policy enforcement is mechanical:
- Organisation Policies constrain allowed regions, resource types, and service enablement — not just documented conventions.
- Resource hierarchy (organisation → folder → project) reflects environment and data-classification separation.
- VPC Service Controls perimeter applied to sensitive APIs (Vertex AI, BigQuery, Cloud Storage with regulated data).
- Audit logging enabled on IAM changes and data-plane operations before any data lands.
-
Data boundaries — for every data store in the design:
- What data classification does it hold (public / internal / confidential / regulated)?
- Is encryption at rest enabled with a customer-managed key (CMEK) where required?
- Are tenant boundaries enforced at the data layer, not just the application layer?
- Does data cross a project or organisation boundary? If yes, is there an explicit data-sharing agreement?
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.
- 8d ago First seen · 83 lines · 59 tokens per session scan A 81276688bdbb
gcp-expert is a skill published in the GitHub repository jpantsjoha/ai-native-developer-experience (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 59 tokens to every session and 1,141 once invoked, about $0.0003 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
last30Days
Resolve "last30Days" to a concrete ISO date range relative to your run time — a rolling 30-day window ending today. Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a "last 30 days" / trailing-month task…
thisWeek
Resolve "thisWeek" to a concrete ISO date range relative to your run time — this week so far (Monday → today). Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a week-to-date task (this week's activity…
comet-hotfix
A quick workflow for fixing an existing bug in Comet, a tool that manages structured code changes. It moves through opening the change, building, checking, and archiving it.
comet-verify
Comet Phase 4: Verify and Close. Invoke with /comet-verify. Verify implementation matches design, handle development branch.
comet-design
A workflow guide for turning an existing software change into a detailed technical design document. It builds on earlier proposal and design files and defines implementation risks, tests, and edge cases.
comet-hotfix
Comet preset path: Bug fix / hotfix. Skip brainstorming, directly open → build → verify → archive. Applicable for behavior fixes, scenarios not involving new capability design.