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/gemini-cli-extensions/google-cloud-storage/gcs-security-assessmentnpx skills add gemini-cli-extensions/google-cloud-storage --skill gcs-security-assessmentgit clone --depth 1 https://github.com/gemini-cli-extensions/google-cloud-storageWrote 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/gemini-cli-extensions/google-cloud-storage/gcs-security-assessment)<a href="https://agentmods.dev/skills/gemini-cli-extensions/google-cloud-storage/gcs-security-assessment"><img src="https://agentmods.dev/badge/skills/gemini-cli-extensions/google-cloud-storage/gcs-security-assessment.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.00181 | $0.01506 |
| Opus 5 | $0.00090 | $0.00753 |
| Sonnet 5 | $0.00036 | $0.00301 |
| Haiku 4.5 | $0.00018 | $0.00151 |
Grade A, and why
gcs-security-assessment 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
89% identical to gcs-security-assessment — 2 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Posture Assessment Skill
You are a Google Cloud Storage security assessment agent trained on Google's Secure AI Framework (SAIF). Your job is to evaluate GCS bucket and project configurations, identify toxic combinations of vulnerabilities, and provide actionable remediation.
[!IMPORTANT]
You are NOT a generic security chatbot. You MUST ground every finding in telemetry signals you have actually gathered. NEVER hallucinate findings or assume configurations you have not verified. If you cannot gather a signal, say so explicitly and skip that check.
[!CAUTION]
CRITICAL: Never execute destructive commands (e.g., rm, rb, IAM policy changes) without first printing the exact command and explicitly asking the user for a Y/N confirmation.
Philosophy
Traditional security tools generate isolated alerts from static rules (e.g., "bucket is public"). You correlate multiple signals to detect toxic combinations — scenarios where individually low-risk configurations combine to create critical exposures. A public bucket storing marketing PDFs is very different from a public bucket storing ML training data with no CMEK, no VPC-SC, and no audit logging.
Phase Summary Table
| Phase | Inputs | Outputs | Reference |
|---|---|---|---|
| 1. Discover Scope & Telemetry | User input (Project ID/Buckets/Datasets) | Scope confirmation, Telemetry signals | references/phases/discover.md |
| 2. Bucket Classification | Telemetry signals | Bucket classifications | references/phases/classification.md |
| 3. Baseline Security Eval | Telemetry signals, Classifications | Baseline failures | references/phases/baseline.md |
| 4. Toxic Combo Analysis | Telemetry signals, Classifications | Toxic combination findings | references/phases/toxic_analysis.md |
| 5. Output | Findings from all phases | Formatted assessment report | references/phases/output.md |
What ships with it
18 files 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.
- examples/sample_assessment.md 6.9 KB
- references/baseline_security.md 4.2 KB
- references/bucket_classification.md 4.6 KB
- references/phases/baseline.md 810 B
- references/phases/classification.md 727 B
- references/phases/discover.md 8.3 KB
- references/phases/output.md 12 KB
- references/phases/toxic_analysis.md 1.8 KB
- references/saif_risk_factors.md 3.7 KB
- references/telemetry_signals.md 4.5 KB
- references/toxic_combinations.md 16 KB
- scripts/cloud_rest_helpers_nodeps.py 20 KB runs code
- scripts/evaluate_project_security_posture.py 17 KB runs code
- scripts/fetch_bucket_telemetry.py 6.6 KB runs code
- scripts/fetch_object_telemetry.py 5.2 KB runs code
- scripts/list_datasets.py 6.7 KB runs code
- scripts/preflight_permissions.py 12 KB runs code
- scripts/validation.py 2.4 KB runs code
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 · 104 lines · 181 tokens per session scan A 401e68c870b8
gcs-security-assessment is a skill published in the GitHub repository gemini-cli-extensions/google-cloud-storage (25 stars, last pushed 4d ago), licensed Apache-2.0. It adds 181 tokens to every session and 1,506 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to gcs-security-assessment, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
conductor-new-track
Plans a new track (feature or bug fix), generates spec/plan documents, and updates the registry.
conductor-implement
Executes the tasks defined in the specified track's plan. Use this to start or continue working on a feature, bug fix, or chore.
conductor-status
Displays the current progress of the project by parsing the Tracks Registry and individual track plans.
impact-audit
Blast radius of a change you have not made yet -- traces a symbol across federated repositories, splits impact per repo, and reports what must ship together.
onboard-repo
Index an unfamiliar codebase into the knowledge graph, then produce a first orientation map -- entry points, most-depended-upon modules, hotspots, test topology.
review-pr
Review a PR or branch diff using the knowledge graph for full structural context. Outputs a structured review with blast-radius analysis.