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 thkt/dotclaude --skill use-cli-gcloudgit clone --depth 1 https://github.com/thkt/dotclaudeWrote 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/thkt/dotclaude/use-cli-gcloud)<a href="https://agentmods.dev/skills/thkt/dotclaude/use-cli-gcloud"><img src="https://agentmods.dev/badge/skills/thkt/dotclaude/use-cli-gcloud/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/thkt/dotclaude/use-cli-gcloud"><img src="https://agentmods.dev/badge/skills/thkt/dotclaude/use-cli-gcloud.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.00036 | $0.00347 |
| Opus 5.5 | $0.00014 | $0.00139 |
| Sonnet 5.5 | $0.00007 | $0.00069 |
| Haiku 4.5 | $0.00004 | $0.00035 |
Grade A, and why
use-cli-gcloud 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 1mo 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.
What it actually says
use-cli-gcloud
コマンド
| 種別 | URL パターン | 既定 | 構造化 |
|---|---|---|---|
| Sheets | docs.google.com/spreadsheets/d/ |
gsheet "URL" (CSV) |
gsheet "URL" json (JSONL、表形式のデータ) |
| Docs | docs.google.com/document/d/ |
gdoc "URL" (text) |
gdoc "URL" md (Markdown、仕様書や文書) |
前提
gsheet と gdoc は shell 関数で、gcloud auth print-access-token からトークンを取る。--help は持たないので、使い方はこのページが正。
落とし穴
認証が切れていると本文でなく Google のエラーページが返り、崩れた CSV や HTML として見える。取得結果が表の形をしていないときは gcloud auth login を促して止まる。
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.
- 1mo ago First seen · 25 lines · 36 tokens per session scan A b5d28964ea55
use-cli-gcloud is a skill published in the GitHub repository thkt/dotclaude (12 stars, last pushed 25d ago), licensed MIT. It adds 36 tokens to every session and 347 once invoked, about $0.0001 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-30.
Other skills, from other repositories
team-management-receiving-feedback
How to receive code review as technical evaluation rather than social performance — verify claims against the codebase before implementing, push back with evidence, and drop the performative agreement. Use when responding to a human reviewer, a PR comment, or another AI reviewer, and when deciding whether a suggestion…
review
Adversarial design review of a System Design Doc. Interrogates the staff questions, finds the cost-explosion and failure risks, returns a verdict. Sensors and evals gate.
council
Five independent critic subagents in parallel on an idea, plan, design, R&R strategy, grant, or SKILL.md, then a synthesis pass that ranks findings by how much of the argument rests on them, never by vote count. A markdown work plan gets the plan roster (assumptions, pre-mortem, what to delete, alternatives per piece…
pr-reviewer
Review pull requests with full context. Fetches linked Jira tickets, Figma designs, and Notion docs via MCP, spawns parallel subagents for systematic code review (correctness, security, tests, SOLID, clean code), then drafts friendly, humanized GitHub-ready comments. Use when reviewing PRs, examining code changes, or…
implementation-review
Pre-commit quality gate. Invoke before every git commit, after /flagrare:staleness-audit. Seven checks, plan gaps, use-case coverage gaps, missing test scenarios, test philosophy violations (Kent Dodds Testing Trophy), SOLID violations, Clean Code violations, and security vulnerabilities. Each check is delegated to a…
security-audit
Focused security review of a change. Finds HIGH-CONFIDENCE, concretely exploitable vulnerabilities in the staged diff (injection, broken authn/authz, secrets and data exposure, unsafe deserialization, crypto misuse, SSRF) and audits dependencies when a lockfile moved, using the repo's own package manager. Runs as…