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-logginggit 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-logging)<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/gcp-cloud-logging"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/gcp-cloud-logging.svg" alt="Measured on agentmods" 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.00062 | $0.01432 |
| Opus 5 | $0.00031 | $0.00716 |
| Sonnet 5 | $0.00012 | $0.00286 |
| Haiku 4.5 | $0.00006 | $0.00143 |
Grade A, and why
gcp-cloud-logging 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 4d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GCP Cloud Logging
MCP Server
- Endpoint:
https://logging.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_log_entries |
Search and retrieve log entries — the primary tool for debugging, error hunting, and audit |
list_log_names |
Discover what logs exist in a project — find available log sources |
get_bucket |
Get details of a specific log bucket (storage container for logs) |
list_buckets |
List all log buckets in a project |
get_view |
Get a specific log view (fine-grained access filter on a bucket) |
list_views |
List log views in a bucket |
Workflow: VPC Flow Log Analysis
When investigating GCP network traffic:
- Discover logs:
list_log_names— findcompute.googleapis.com/vpc_flows - Query flow logs:
list_log_entriesfiltered by:- Source/destination IP
- Port and protocol
- Action (ALLOWED/DENIED)
- Time range
- Denied traffic: Filter for
reporter="DEST"and denied connections - Top talkers: Aggregate by source/destination IP and bytes
- Cross-reference: Use
gcp-cloud-monitoringfor network metrics during the same period - Report: Traffic analysis with security findings
Workflow: Firewall Log Investigation
When investigating GCP firewall rule activity:
- Discover logs:
list_log_names— findcompute.googleapis.com/firewall - Query firewall logs:
list_log_entriesfiltered by:- Rule name
- Action (ALLOWED/DENIED)
- Source/destination IP
- Port
- Denied connections: Find blocked traffic patterns
- Rule effectiveness: Which rules are hitting most frequently?
- Report: Firewall activity summary with recommendations
Workflow: Audit Trail Investigation
When investigating GCP API activity (equivalent of AWS CloudTrail):
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.
- 4d ago First seen · 131 lines · 62 tokens per session scan A d5ac07a7b075
gcp-cloud-logging is a skill published in the GitHub repository automateyournetwork/netclaw (650 stars, last pushed yesterday), licensed Apache-2.0. It adds 62 tokens to every session and 1,432 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
analyzing-kubernetes-audit-logs
Parses Kubernetes API server audit logs (JSON lines) to detect exec-into-pod, secret access, RBAC modifications, privileged pod creation, and anonymous API access. Builds threat detection rules from audit event patterns. Use when investigating Kubernetes cluster compromise or building k8s-specific SIEM detection rules.
gke-ai-troubleshooting-jobset-interruption
Diagnoses GKE JobSet interruptions, restarts, and preemptions for AI/ML training workloads autonomously. Use when troubleshooting JobSet restart loops, spot VM preemptions, node readiness failures, host VM issues, or coordinator worker crashes. Don't use for general GKE cluster creation, basic workload deployment, or…
gke-workload-troubleshooting
Diagnoses GKE workload failures (CrashLoopBackOff, OOMKilled, ImagePullBackOff, Pending, etc.) via logs and events. Use when pods fail to start or crash repeatedly. Don't use for GKE cluster infrastructure provisioning, node pool creation, or non-Kubernetes Google Cloud services.
gke-node-notready
Diagnoses GKE nodes reporting NotReady or Unknown status by inspecting node conditions, events, kubelet/containerd logs, and node metrics, then proposing safe remediations. Use when nodes show NotReady, when the kubelet stops posting node status, or when workloads are evicted or stuck Pending due to node health. Don't…
agentcore-investigation
Investigate Bedrock AgentCore runtime sessions via CloudWatch Logs Insights — resolve session/trace IDs, query OTEL spans, filter noise, build timelines. Use when debugging AgentCore agent sessions, tracing tool calls, or analyzing latency.
network-rca
Kubernetes network root cause analysis skill powered by Kubeshark MCP. Use this skill whenever the user wants to investigate past incidents, perform retrospective traffic analysis, take or manage traffic snapshots, extract PCAPs, dissect L7 API calls from historical captures, compare traffic patterns over time, detect…