google-cloud-filestore-autoscale

google-cloud-filestore-autoscale is a skill for Claude Code, Codex from google/skills. It costs 102 tokens per session (2,948 once invoked), scanned A, original, Apache-2.0.

An automation workflow for inspecting Google Cloud Filestore storage capacity and usage. Filestore is managed file storage that applications can access over a network.

In plain words
What is it for?
Checking Filestore headroom, reading usage metrics, increasing or decreasing instance capacity, and applying attribution tags to the related commands or requests.
Why use it?
It helps maintain enough free storage and reduce waste by evaluating capacity against defined scaling thresholds.

Skill for Claude CodeCodex ✓ vendor

Written for no agent in particular: nothing here depends on one.

Good fit Checking Filestore headroom, reading usage metrics, increasing or decreasing instance capacity, and applying attribution tags to the related commands or requests.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/google/skills/google-cloud-filestore-autoscale
About the project

google/skills is a collection of Agent Skills that guide AI agents in using Google products and technologies, including Google Cloud services. Developers and agents use these reusable workflows for tasks such as cloud authentication, data analysis, application deployment, and AI platform management. The catalogue entries are skills, plugins, and an MCP integration from this collection.

google/skills · 21,550 stars · on GitHub

Install

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.

Any agent
npx skills add google/skills --skill google-cloud-filestore-autoscale
Clone the repo
git clone --depth 1 https://github.com/google/skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for google-cloud-filestore-autoscale

README.md
[![agentmods](https://agentmods.dev/badge/skills/google/skills/google-cloud-filestore-autoscale/github.svg)](https://agentmods.dev/skills/google/skills/google-cloud-filestore-autoscale)
Your own site
<a href="https://agentmods.dev/skills/google/skills/google-cloud-filestore-autoscale"><img src="https://agentmods.dev/badge/skills/google/skills/google-cloud-filestore-autoscale/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.

agentmods 80×15 button for google-cloud-filestore-autoscale

Your own site · 80×15
<a href="https://agentmods.dev/skills/google/skills/google-cloud-filestore-autoscale"><img src="https://agentmods.dev/badge/skills/google/skills/google-cloud-filestore-autoscale.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 102 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,948 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 7 Oct 2026
  • Snyk pass 7 Oct 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00102 $0.02948
Opus 5.5 $0.00041 $0.01179
Sonnet 5.5 $0.00020 $0.00590
Haiku 4.5 $0.00010 $0.00295

Measured 18d ago against content hash aef9a703fc01, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

google-cloud-filestore-autoscale scanned grade A with 1 finding 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 18d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

runtime-specific options including GCP REST API, `gcloud`, `curl`, and MCP
skills/cloud/google-cloud-filestore-autoscale/SKILL.md · 223 lines

How it starts

The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Filestore Autoscale

This skill enables agents to inspect, evaluate, and modify Filestore instance capacities across Google Cloud projects based on configured thresholds.

Prerequisites / IAM Requirements

Before an agent or user can execute this skill, their runtime Service Account must possess the following IAM roles on the target project(s):

  • roles/file.editor (Required for listing instances and triggering scale up/down updates)
  • roles/monitoring.viewer (Required for reading Cloud Monitoring capacity metrics used_bytes)
  • roles/mcp.toolUser (Required if utilizing backend Filestore MCP tools)

Quick Start

  1. Ensure gcloud is installed. See gcloud installation guide if needed.

  2. Enable essential APIs:

    gcloud services enable file.googleapis.com monitoring.googleapis.com --quiet
    
  3. Inspect fleet capacity and free space (see "Discovery & Read Operations" below).

  4. Evaluate against configured up/down capacity thresholds.

  5. Scale target instances and apply attribution tags.

Attribution

Tag every Cloud Filestore command or API request provided or executed. Prefix gcloud commands with the correct metrics environment targeting this skill:

CLOUDSDK_METRICS_ENVIRONMENT="gcs-skills gcs-skills/1.0 (skill:google-cloud-filestore-autoscale)" \
gcloud filestore instances update ...

On direct HTTP calls to the REST API, append the User-Agent:

User-Agent: gcs-skills/1.0 (skill:google-cloud-filestore-autoscale)

Conceptual & Informational Queries (CRITICAL)

For purely conceptual, educational, or informational questions (e.g., "What are Filestore scaling limits?", "Can Basic instances scale down?", "Explain Filestore Tiers"):

  • Rule: Answer immediately using your pre-trained knowledge and the matrix below.
  • Constraint: Do not execute external tool calls or API requests for basic knowledge questions.

Read the full file on GitHub · 223 lines

Files

What ships with it

3 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.

Changes

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.

  1. 18d ago Changed · +1 tokens per session aef9a703fc01
  2. 1mo ago Changed · +1 lines c180b6e61958
  3. 1mo ago First seen · 222 lines · 101 tokens per session scan A 28e9703e70f4

Subscribe to this mod's changes

google-cloud-filestore-autoscale is a skill published in the GitHub repository google/skills (21,550 stars, last pushed yesterday), licensed Apache-2.0. It adds 102 tokens to every session and 2,948 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

azure-local

Expert knowledge for Azure Local development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when planning Azure Local clusters, SDN networking, multi-rack/disconnected setups, Arc…

MicrosoftDocs/Agent-Skills · 107 tokens

azure-stack-edge

Expert knowledge for Azure Stack Edge development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when deploying IoT Edge modules, GPU/Kubernetes apps, DeepStream workloads, Arc GitOps, or local ARM integrations…

MicrosoftDocs/Agent-Skills · 124 tokens

azure-operator-service-manager

Expert knowledge for Azure Operator Service Manager development including troubleshooting, best practices, security, configuration, and integrations & coding patterns. Use when onboarding CNFs/VNFs with Helm, managing ACR artifacts, configuring cluster registry, Private Link, or RBAC, and other Azure Operator Service…

MicrosoftDocs/Agent-Skills · 108 tokens

azure-route-server

Expert knowledge for Azure Route Server development including troubleshooting, best practices, architecture & design patterns, limits & quotas, security, and configuration. Use when designing Route Server topologies, BGP peering and policies, route maps, RBAC access, or capacity limits, and other Azure Route Server…

MicrosoftDocs/Agent-Skills · 111 tokens

scheduled-jobs

Covers cron and scheduled work done right — idempotency, preventing overlapping runs, monitoring for missed and failed runs, alerting on silence, and getting time zones and DST transitions correct. Use this whenever the user is writing a cron job or Kubernetes CronJob, asks why a scheduled job ran twice or didn't run…

arjunprabhulal/devops-skills · 121 tokens

gitops

Establishes Git as the single source of truth for deployed state, with a pull-based controller reconciling the cluster to match a repo instead of humans or pipelines pushing changes via kubectl or helm. Use this whenever the user designs a deployment repo layout, asks how environments should be promoted, debates…

arjunprabhulal/devops-skills · 122 tokens