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 porcupine-md/jonggrang --skill gcp-deploymentgit clone --depth 1 https://github.com/porcupine-md/jonggrangWrote 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/porcupine-md/jonggrang/gcp-deployment)<a href="https://agentmods.dev/skills/porcupine-md/jonggrang/gcp-deployment"><img src="https://agentmods.dev/badge/skills/porcupine-md/jonggrang/gcp-deployment/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/porcupine-md/jonggrang/gcp-deployment"><img src="https://agentmods.dev/badge/skills/porcupine-md/jonggrang/gcp-deployment.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.00024 | $0.00658 |
| Opus 5 | $0.00012 | $0.00329 |
| Sonnet 5 | $0.00005 | $0.00132 |
| Haiku 4.5 | $0.00002 | $0.00066 |
Grade A, and why
gcp-deployment scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. Cloud Run: Check the returned service URL via `curl` and inspect `gcloud logging read "resource.type=cloud_run_revision AND resource.labels.service_name=<SERVICE_NAME>"` if it fails. How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
Deploying {{project_name}} ({{project_type}}) to Google Cloud Platform (GCP). You will follow a strict 6-phase Deployment Lifecycle Contract.
Instructions
Execute the following phases in order:
Phase 1: Authentication
- Ensure the
GOOGLE_APPLICATION_CREDENTIALSenvironment variable is set to a valid service account key JSON file, or configure Workload Identity Federation (if inside CI/CD). - Authenticate the gcloud CLI:
gcloud auth activate-service-account --key-file=$GOOGLE_APPLICATION_CREDENTIALS. - Set the default project:
gcloud config set project <PROJECT_ID>.
Phase 2: Build
- Prepare the artifacts for deployment.
- If Cloud Run or GKE: build your Docker image (e.g.,
docker build -t gcr.io/<PROJECT_ID>/<APP_NAME> .orgcloud builds submit --tag gcr.io/<PROJECT_ID>/<APP_NAME>). - If App Engine: prepare
app.yaml. - If Static Site (Cloud Storage): run
npm run build.
Phase 3: Install / Provisioning
- Ensure the target GCP resources (Cloud Run services, Buckets, Compute Instances) exist and you have permissions to write to them.
- If Cloud Storage:
gsutil ls gs://<bucket-name>. - Enable necessary APIs (e.g.,
gcloud services enable run.googleapis.comif using Cloud Run).
Phase 4: Deploy
- Ship the artifact to GCP.
- Cloud Run:
gcloud run deploy <SERVICE_NAME> --image gcr.io/<PROJECT_ID>/<APP_NAME> --region <REGION> --platform managed. - App Engine:
gcloud app deploy. - Cloud Storage:
gsutil rsync -R dist/ gs://<bucket-name>.
Phase 5: Checking
- Verify the deployment was successful.
- Cloud Run: Check the returned service URL via
curland inspectgcloud logging read "resource.type=cloud_run_revision AND resource.labels.service_name=<SERVICE_NAME>"if it fails. - App Engine: Check the target URL.
- Ensure the service returns HTTP 200.
Phase 6: Update / Rollback
- If Phase 5 fails, immediately initiate a rollback.
- Cloud Run: Route 100% of traffic to the previous revision (
gcloud run services update-traffic <SERVICE_NAME> --to-revisions=<PREVIOUS_REVISION_NAME>=100 --region <REGION>). - App Engine: Roll back traffic to an older version via
gcloud app services set-traffic. - Note the failure in the progress log.
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 · 57 lines · 24 tokens per session scan A 52da54baf136
gcp-deployment is a skill published in the GitHub repository porcupine-md/jonggrang (11 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 658 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…