gcp-logs

gcp-logs is a skill for Claude Code from eveld/claude. It costs 29 tokens per session (1,088 once invoked), scanned A, original, MIT.

A Google Cloud Logging query helper for application errors, service logs, and request traces. Google Cloud Logging is the service that stores logs from applications and infrastructure running on Google Cloud.

In plain words
What is it for?
Use it to investigate errors, find request traces, examine service behaviour over time, and correlate events between services.
Why use it?
It helps investigate failures and follow requests across services without manually searching unrelated log entries.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the workflows plugin — 29 skills, 5 commands, 17 agents shipped together

Good fit Use it to investigate errors, find request traces, examine service behaviour over time, and correlate events between services.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/eveld/claude/gcp-logs
View source ↗ eveld/claude
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 eveld/claude --skill gcp-logs
Clone the repo
git clone --depth 1 https://github.com/eveld/claude

Made for: Claude Code.

Or install workflows, the plugin that ships this one along with the rest of its 29 skills, 5 commands, 17 agents.

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 gcp-logs

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/eveld/claude/gcp-logs"><img src="https://agentmods.dev/badge/skills/eveld/claude/gcp-logs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,088 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00029 $0.01088
Opus 5 $0.00015 $0.00544
Sonnet 5 $0.00006 $0.00218
Haiku 4.5 $0.00003 $0.00109

Measured 8d ago against content hash 18a919430a16, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

gcp-logs 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 8d 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.

skills/gcp-logs/SKILL.md · 124 lines

How it starts

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

Query GCP Logs

Search GCP Cloud Logging for application errors, service logs, and traces.

When to Use

  • Investigating errors in GCP-hosted services
  • Finding request traces for debugging
  • Analyzing service behavior over time
  • Correlating events across services

Pre-flight Checks

Authentication and Context

# Check gcloud auth
gcloud auth list 2>/dev/null | grep -q ACTIVE || {
  echo "Not authenticated. Run: gcloud auth login"
  exit 1
}

# Show current project
CURRENT_PROJECT=$(gcloud config get-value project 2>/dev/null)
echo "Current GCP Project: $CURRENT_PROJECT"

# If context suggests different project, prompt to switch
# Example: User mentions "production" but current project is "staging"
# Detect from query context and prompt:
# echo "Query mentions 'production' but current project is '$CURRENT_PROJECT'"
# echo "Switch to production project? Run: gcloud config set project example-production"
# read -p "Continue with current project? (y/n) " -n 1 -r

Query Strategy

Follow this approach for effective log queries:

  1. Start simple: Begin with basic filters (severity, service, timestamp)
  2. Verify data exists: Check if logs are available in your time range
  3. Narrow time windows: Use 1-2 hour windows for better performance
  4. Use two-stage filtering: For complex logic, query broad → filter with jq
  5. Save to files: Store large result sets for analysis
  6. Iterate: Start broad, progressively add filters

Example Workflow

# Step 1: Check if ANY logs exist in time range
gcloud logging read 'timestamp>="2025-12-24T10:00:00Z"' --limit=10

# Step 2: Filter to specific service
gcloud logging read 'resource.labels.container_name="api-gateway"' --limit=50

# Step 3: Add severity filter
gcloud logging read 'resource.labels.container_name="api-gateway" AND severity>=ERROR' --limit=100

# Step 4: Narrow time window
gcloud logging read \
  'resource.labels.container_name="api-gateway" AND severity>=ERROR AND timestamp>="2025-12-24T10:00:00Z" AND timestamp<="2025-12-24T11:00:00Z"' \
  --limit=100 \
  --format=json

Read the full file on GitHub · 124 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. 8d ago First seen · 124 lines · 29 tokens per session scan A 18a919430a16

Subscribe to this mod's changes

gcp-logs is a skill published in the GitHub repository eveld/claude (10 stars, last pushed 7mo ago), licensed MIT. It adds 29 tokens to every session and 1,088 once invoked, about $0.0001 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.