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 agentmods add skills/saski/arnesto/gcloud-auth-verificationnpx skills add saski/arnesto --skill gcloud-auth-verificationgit clone --depth 1 https://github.com/saski/arnestoWrote 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/saski/arnesto/gcloud-auth-verification)<a href="https://agentmods.dev/skills/saski/arnesto/gcloud-auth-verification"><img src="https://agentmods.dev/badge/skills/saski/arnesto/gcloud-auth-verification.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 | $0.00046 | $0.00451 |
| Opus 5 | $0.00023 | $0.00226 |
| Sonnet 5 | $0.00009 | $0.00090 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
gcloud-auth-verification 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 5d 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 gcloud-auth-verification — 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.
What it actually says
Handling Authentication Issues
Common Error Messages
- gcloud/bq CLI:
ERROR: (bq) You do not currently have an active account selected.No credentialed accounts.Configuration error: No account is currently active.
- Execution Failures (Python/Notebooks):
google.auth.exceptions.DefaultCredentialsError: Could not automatically determine credentials.Forbidden: 403 Access Denied(when it's clearly an auth issue).
Verification Step
Before asking the user to log in, independently verify the authentication status
by running: gcloud auth list * If the output contains No credentialed accounts., proceed to the Corrective Action steps below. * If an account
is listed but the user still receives a 403 Access Denied error, the issue
is likely IAM permissions (e.g., missing BigQuery roles) on their active
account, rather than missing authentication. In this case, investigate the
permissions rather than asking them to log in again.
Corrective Action
When missing credentials are confirmed, DO NOT attempt to fix the credentials via code or alternative tools. Credentials must be established by the user.
Stop and ask the user to run the following commands in their terminal:
-
To authenticate the gcloud CLI:
gcloud auth login -
To set up Application Default Credentials (ADC) (required for BQ CLI AND most libraries/notebooks):
gcloud auth application-default login
Post-Login Verification
After the user confirms they have logged in, verify with: gcloud auth list
Then proceed with the original task.
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.
- 5d ago First seen · 52 lines · 46 tokens per session scan A fcdd8ae4407e
gcloud-auth-verification is a skill published in the GitHub repository saski/arnesto (5 stars, last pushed 9d ago), licensed Unlicense. It adds 46 tokens to every session and 451 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to gcloud-auth-verification, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
eng-runbook
An engineering runbook — service overview, alerts table, dashboards links, common procedures with copy-pasteable commands, on-call rotation, and an incident-response checklist. Use when the brief mentions "runbook", "ops doc", "on-call guide", "SRE doc", or "运维手册".
terraform-skill
Use when working with Terraform or OpenTofu - creating modules, writing tests (native test framework, Terratest), setting up CI/CD pipelines, reviewing configurations, choosing between testing approaches, debugging state issues, implementing security scanning (trivy, checkov), or making infrastructure-as-code…
alicloud_cli
阿里云 CLI 中文文档镜像检索与命令辅助：先走章节索引，再下钻正文页面，给出命令前必须有本地文档证据。.
terraform-cli-setup
Terraform CLI 安装与初始化技能。当用户本地未安装 Terraform 时自动完成安装，确保 terraform 命令可用并能执行 init/validate。不负责 Provider 凭证配置，凭证在实际使用时由 terraform-skill 引导。.
aiq-deploy
Use when asked to install, deploy, run, validate, troubleshoot, or stop NVIDIA AI-Q Blueprint infrastructure.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.