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/jpantsjoha/googlecloud-plugin/iamnpx skills add jpantsjoha/googlecloud-plugin --skill iamgit clone --depth 1 https://github.com/jpantsjoha/googlecloud-pluginWhat 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.00106 | $0.00687 |
| Opus 5 | $0.00053 | $0.00344 |
| Sonnet 5 | $0.00021 | $0.00137 |
| Haiku 4.5 | $0.00011 | $0.00069 |
Grade A, and why
iam 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 yesterday.
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
IAM — Identity and Access Management
Control who (identity) can do what (role) on which GCP resource. Always least-privilege.
Principles
- Least privilege — grant the minimum role needed. Prefer predefined roles over basic roles. Never grant
roles/ownerorroles/editorprogrammatically. - Service accounts for workloads — not user accounts. Use Workload Identity to avoid SA key files.
- IAM Conditions — scope bindings by resource, time, or request attribute where possible.
- Audit regularly —
gcloud projects get-iam-policyto review bindings; remove stale grants.
Core Patterns
Grant a predefined role
gcloud projects add-iam-policy-binding PROJECT_ID \
--member="serviceAccount:[email protected]" \
--role="roles/run.invoker"
Create a service account
gcloud iam service-accounts create SA_NAME \
--display-name="Description" \
--project PROJECT_ID
List effective permissions on a resource
gcloud projects get-iam-policy PROJECT_ID \
--flatten="bindings[].members" \
--format="table(bindings.role,bindings.members)"
IAM Condition (time-bound access)
gcloud projects add-iam-policy-binding PROJECT_ID \
--member="user:[email protected]" \
--role="roles/viewer" \
--condition="expression=request.time < timestamp('2026-12-31T00:00:00Z'),title=temp-access"
Never Do
- Grant
roles/ownerorroles/editorto service accounts or automation - Create SA key files when Workload Identity is available
- Share service account keys across environments
References
What ships with it
1 file 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.
- yesterday First seen · 70 lines · 106 tokens per session scan A 8bd46744c8bc
iam is a skill published in the GitHub repository jpantsjoha/googlecloud-plugin (4 stars, last pushed 24d ago), licensed MIT. It adds 106 tokens to every session and 687 once invoked, about $0.0005 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-31.
Other skills, from other repositories
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
multi-reviewer-patterns
Coordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated reporting. Use this skill when organizing multi-reviewer code reviews, calibrating finding severity, or consolidating review results.
avoid-ai-writing
Audit and rewrite prose so it stops reading as machine-generated. Use this skill when asked to remove AI-isms, clean up AI writing, edit a draft for AI tells, audit a README, changelog, release note, PR description, or blog post for machine-sounding prose, or make text sound less like AI. Supports a detect-only mode…
clonedeps
Clone important project dependency source code into an ignored local workspace so OpenCode can inspect library internals. Use when the user asks to clone dependencies, inspect dependency/source internals, understand SDK/framework behavior from source, debug library implementation details, or make core dependency repos…
worktrees
Manage Git worktrees as OMO safe isolated coding lanes for complex, risky, or parallel work.