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 divinevideo/divine-mobile --skill gcloud-builds-tag-deploy-false-successgit clone --depth 1 https://github.com/divinevideo/divine-mobileWrote 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/divinevideo/divine-mobile/gcloud-builds-tag-deploy-false-success)<a href="https://agentmods.dev/skills/divinevideo/divine-mobile/gcloud-builds-tag-deploy-false-success"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/gcloud-builds-tag-deploy-false-success/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/divinevideo/divine-mobile/gcloud-builds-tag-deploy-false-success"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/gcloud-builds-tag-deploy-false-success.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00191 | $0.02209 |
| Opus 5 | $0.00096 | $0.01104 |
| Sonnet 5 | $0.00038 | $0.00442 |
| Haiku 4.5 | $0.00019 | $0.00221 |
Grade A, and why
gcloud-builds-tag-deploy-false-success 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.
How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gcloud builds submit --tag false-success trap
Problem
A common Cloud Run deploy recipe looks like this:
gcloud builds submit --tag us-central1-docker.pkg.dev/PROJECT/REPO/IMAGE:latest
gcloud run services update SERVICE \
--image us-central1-docker.pkg.dev/PROJECT/REPO/IMAGE:latest \
--region us-central1 --project PROJECT
When the first command fails (most commonly because the current working directory doesn't
contain a Dockerfile), its single-line error scrolls off-screen above the second command's
verbose progress spinner. The second command then pulls the existing :latest image
from Artifact Registry — which is the previous build — and deploys it. You get:
✓ Deploying... Done.
✓ Creating Revision...
✓ Routing traffic...
Service [...] revision [...] has been deployed and is serving 100 percent of traffic.
A green "SUCCESS" deploy that did not change the running code. The user then spends hours debugging why the fix isn't live, or worse, concludes the fix doesn't work and reverts good code.
Context / Trigger Conditions
- User reports "I deployed the fix but production behavior is unchanged"
- Recent shell output contains both:
ERROR: (gcloud.builds.submit) Invalid value for [source]: Dockerfile required when specifying --tagrevision [...] has been deployed and is serving 100 percent of traffic
- The
gcloud builds submit --tag …was run without a source positional argument AND the working directory does not contain the Dockerfile (common in monorepos where the Dockerfile lives under a subdirectory likecloud-run-upload/,services/api/, etc.) - The deploy targets use the mutable
:latesttag (or another tag that already exists in the registry)
Root cause
gcloud builds submit --tag IMAGE_TAG needs a source directory. When you omit it, it
defaults to the current working directory, and if there's no Dockerfile there (or a
cloudbuild.yaml), it exits immediately with exit code 1 — without uploading anything,
without creating a build job, without touching Artifact Registry.
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 · 198 lines · 191 tokens per session scan A 9b999c24a98a
gcloud-builds-tag-deploy-false-success is a skill published in the GitHub repository divinevideo/divine-mobile (265 stars, last pushed today), licensed MPL-2.0. It adds 191 tokens to every session and 2,209 once invoked, about $0.0010 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
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-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).
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…
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".
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
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…