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 N-O-P-E/nope-marketplace --skill gcp-setupgit clone --depth 1 https://github.com/N-O-P-E/nope-marketplaceWrote 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/n-o-p-e/nope-marketplace/gcp-setup)<a href="https://agentmods.dev/skills/n-o-p-e/nope-marketplace/gcp-setup"><img src="https://agentmods.dev/badge/skills/n-o-p-e/nope-marketplace/gcp-setup/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/n-o-p-e/nope-marketplace/gcp-setup"><img src="https://agentmods.dev/badge/skills/n-o-p-e/nope-marketplace/gcp-setup.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.00161 | $0.06201 |
| Opus 5.5 | $0.00064 | $0.02480 |
| Sonnet 5.5 | $0.00032 | $0.01240 |
| Haiku 4.5 | $0.00016 | $0.00620 |
Grade A, and why
gcp-setup 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 2mo 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 — 495 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GCP Setup — Browser-Automated Google Cloud Configuration
Walks through Google Cloud Console in the browser so the user doesn't have to click through dozens of screens. The user describes what they need, you figure out the steps, then drive Chrome through each one.
Before You Start
Check these before opening the browser. If anything is missing, tell the user what to do first.
You need:
- Chrome browser running
- Chrome DevTools MCP extension active and connected (verify with
list_pages) - A Google account with access to GCP
- A billing account (if creating a new project or enabling paid APIs)
- Your organization ID (if working within a Google Workspace org — find it at
https://console.cloud.google.com/cloud-resource-manager)
Check for an existing setup summary: look for .gcp-setup.md in the project root. If it exists, read it — it may contain project IDs, service account emails, and previously enabled APIs that let you skip questions and avoid duplicating work.
Invocation Modes
This skill works in two modes:
Mode 1: Direct invocation (/gcp-setup)
The user explicitly asks to set up GCP. Start with the Common Setups section below, then Discovery.
Mode 2: Context-aware invocation (/gcp-setup during feature work)
You're mid-feature (building an app, deploying a service, etc.) and realize GCP infrastructure is needed — or the user invokes /gcp-setup after you've told them what cloud resources the feature requires.
In this mode, skip most discovery questions because you already know the answers from the feature context. Instead:
- Analyze the current context — what are you building? What files have you been working on? What does the feature need?
- Derive the GCP requirements automatically:
- Scan the codebase for imports/config that imply GCP services (e.g.,
@google-cloud/firestore→ Firestore API,@google-cloud/storage→ Cloud Storage API) - Check for existing GCP config files (
app.yaml,cloudbuild.yaml,.gcloudignore,Dockerfile, environment variables referencingGOOGLE_CLOUD_PROJECT, etc.) - Look at package.json, requirements.txt, go.mod, etc. for GCP SDK dependencies
- Check for existing service account references in CI/CD configs (
.github/workflows/,Makefile, etc.) - See
references/codebase-signals.mdfor the full lookup table
- Scan the codebase for imports/config that imply GCP services (e.g.,
- Present what you've figured out:
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.
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.
- 2mo ago First seen · 495 lines · 161 tokens per session scan A 71eefceb9242
gcp-setup is a skill published in the GitHub repository N-O-P-E/nope-marketplace (9 stars, last pushed 6mo ago), licensed MIT. It adds 161 tokens to every session and 6,201 once invoked, about $0.0006 per session on Opus 5.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-31.
Other skills, from other repositories
stealth-browser-mcp
Use this skill when operating stealth-browser-mcp from an AI agent or MCP client for browser automation, page inspection, element interaction, screenshots, file uploads, CDP commands, network debugging, cookies/storage, stealth setup, or reliable multi-step browser workflows. It provides the correct tool order, state…
event-driven-architecture
Kafka, RabbitMQ, SQS/SNS, event sourcing, CQRS, saga patterns, dead letter queues, and idempotency. Use when designing asynchronous systems, implementing message-driven workflows, or building event streaming pipelines.
devops-cloud
DevOps, cloud infrastructure, and platform engineering. Use when working with AWS, GCP, Azure, Kubernetes, Terraform, CI/CD pipelines, or infrastructure as code.
agent-cloud-architect
Specialist subagent: Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes…
agent-e2e-test-specialist
Specialist subagent: Playwright, Cypress, and visual regression testing specialist. Use only when the user explicitly asks for E2E tests, browser test automation, or visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.
edge-computing
Edge computing with Cloudflare Workers, Deno Deploy, Bun, Vercel Edge Functions, AWS Lambda@Edge, and edge databases (Turso, D1, DynamoDB Global Tables). Use when building low-latency edge applications, edge-side rendering, or globally distributed compute.