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 automateyournetwork/netclaw --skill gcp-cloud-monitoringgit clone --depth 1 https://github.com/automateyournetwork/netclawWrote 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/automateyournetwork/netclaw/gcp-cloud-monitoring)<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/gcp-cloud-monitoring"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/gcp-cloud-monitoring/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/automateyournetwork/netclaw/gcp-cloud-monitoring"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/gcp-cloud-monitoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00055 | $0.01163 |
| Opus 5 | $0.00028 | $0.00581 |
| Sonnet 5 | $0.00011 | $0.00233 |
| Haiku 4.5 | $0.00006 | $0.00116 |
Grade A, and why
gcp-cloud-monitoring 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GCP Cloud Monitoring
MCP Server
- Endpoint:
https://monitoring.googleapis.com/mcp(Streamable HTTP) - Auth: OAuth 2.0 via Google IAM — service account key (
GOOGLE_APPLICATION_CREDENTIALS) orgcloud auth application-default login - Requires:
GCP_PROJECT_IDenvironment variable
Available Tools (6)
| Tool | What It Does |
|---|---|
list_timeseries |
Query time series data — CPU, memory, network, disk metrics for any GCP resource |
list_metric_descriptors |
Discover available metric types in a project — find what you can monitor |
list_alert_policies |
List all alerting policies — conditions, notification channels, thresholds |
get_alert_policy |
Get details of a specific alerting policy |
list_alerts |
List current and past alert violations — what's firing right now |
get_alert |
Get details of a specific alert violation |
Workflow: GCP Network Monitoring
When a user asks "how is our GCP network performing?":
- Check alerts:
list_alertsto find any active alert violations - VM network metrics:
list_timeseriesforcompute.googleapis.com/instance/network/received_bytes_countandsent_bytes_count - Packet drops:
list_timeseriesforcompute.googleapis.com/instance/network/received_packets_dropped_count - Firewall metrics:
list_timeseriesforcompute.googleapis.com/firewall/dropped_packets_count - Load balancer metrics:
list_timeseriesforloadbalancing.googleapis.com/https/request_countandtotal_latencies - Report: Network health dashboard with any issues flagged
Workflow: Alert Investigation
When investigating GCP alerts:
- List active alerts:
list_alerts— find what's currently firing - Get alert details:
get_alert— condition, threshold, resource affected - Get policy:
get_alert_policy— what triggers this alert, notification channels - Pull metrics:
list_timeseriesfor the affected metric — see the spike/anomaly - Cross-reference: Use
gcp-cloud-loggingfor correlated log entries - Report: Alert investigation with root cause and timeline
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.
- 9d ago First seen · 90 lines · 55 tokens per session scan A cdcc0c0a5f53
gcp-cloud-monitoring is a skill published in the GitHub repository automateyournetwork/netclaw (657 stars, last pushed 6d ago), licensed Apache-2.0. It adds 55 tokens to every session and 1,163 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
huawei-cloud-cce-metric-analyzer
Huawei Cloud CCE Metric analysis skill using the Python dispatcher with hcloud-backed cloud service queries. Use this skill when the user wants to: (1) query Pod/Node/CoreDNS/nginx-ingress/autoscaler/control-plane CPU, memory, disk, QPS, latency, request, connection, certificate, scaling, or error-rate metrics, (2)…
Observability & Monitoring
Structured logging, metrics, distributed tracing, and alerting strategies.
Observability with Prometheus & Grafana
Production-grade observability stack with Prometheus metrics, Grafana dashboards, PromQL query language, alerting rules, and AI-powered anomaly detection for modern cloud-native applications.
querying-yandex-cloud
Read Yandex Cloud through its REST API. Applies to any question about VMs, metrics, logs, audit events, Kubernetes, managed databases, serverless, networking or any other Yandex Cloud resource. Never shell out to the yc CLI — it is not how this agent reaches Yandex Cloud and is usually not installed.
opentelemetry-net-instrumentation
Provides guidance for implementing OpenTelemetry instrumentation in .NET codebases, covering tracing (Activities/Spans), metrics, logs, naming conventions, error handling, performance, SDK setup, resources, context propagation, and API design best practices.
auditing-gcp-iam-permissions
Auditing Google Cloud Platform IAM permissions to identify overly permissive bindings, primitive role usage, service account key proliferation, and cross-project access risks using gcloud CLI, Policy Analyzer, and IAM Recommender.