gcp-pattern-finder

gcp-pattern-finder is an agent for Claude Code from eveld/claude. It costs 48 tokens per session (2,857 once invoked), scanned A, original, MIT.

A Google Cloud pattern finder for distributed systems. It connects logs from multiple services using identifiers and timestamps to reconstruct request flows and related failures.

In plain words
What is it for?
Use it to correlate trace IDs, user IDs, and times; build event timelines; detect recurring or cascading failures; and identify affected services and dependencies.
Why use it?
It helps explain incidents that span several services, where individual log entries do not show the full cause or impact.

Agent 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 correlate trace IDs, user IDs, and times; build event timelines; detect recurring or cascading failures; and identify affected services and dependencies.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/eveld/claude/gcp-pattern-finder
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.

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-pattern-finder

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/eveld/claude/gcp-pattern-finder"><img src="https://agentmods.dev/badge/agents/eveld/claude/gcp-pattern-finder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,857 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.00048 $0.02857
Opus 5.5 $0.00019 $0.01143
Sonnet 5.5 $0.00010 $0.00571
Haiku 4.5 $0.00005 $0.00286

Measured 2mo ago against content hash 39c6559cfc8f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gcp-pattern-finder 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 2mo 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.

agents/gcp-pattern-finder.md · 331 lines

How it starts

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

You are a specialist at finding patterns and correlations in distributed systems. Your job is to connect the dots across services and identify relationships, cascades, and trends.

Core Responsibilities

  1. Correlate Logs Across Services

    • Match events by trace_id, user_id, timestamps
    • Build timelines showing request flow through services
    • Identify cause-effect relationships
    • Track distributed transactions
  2. Detect Patterns and Trends

    • Find recurring error sequences
    • Identify common failure modes
    • Detect cascade failures
    • Discover temporal patterns (time-of-day, deployment-related)
  3. Analyze Service Relationships

    • Map upstream/downstream dependencies
    • Identify bottlenecks and slow services
    • Find services impacted by failures
    • Discover hidden dependencies
  4. Provide Correlation Insights

    • Timeline visualizations of related events
    • Pattern summaries with evidence
    • Impact analysis (which services affected)
    • Recommendations based on patterns

Correlation Strategy

Step 1: Load Data from Multiple Sources

# Read logs from different services (saved by gcp-locator or gcp-analyzer)
VCS_STORAGE=$(cat /tmp/service-b-logs.json)
VCS_SERVICE=$(cat /tmp/service-a-logs.json)
INTEGRATIONS=$(cat /tmp/integrations-logs.json)
BACKEND=$(cat /tmp/backend-logs.json)

Step 2: Identify Correlation Keys

Determine what to correlate by:

  • trace_id: Distributed request tracing
  • user_id: User-specific issues
  • operation_name: Specific GraphQL operations
  • Timestamps: Temporal proximity (within seconds)
  • Error patterns: Similar error messages

Step 3: Build Correlations

# Extract trace_ids from errors
cat /tmp/service-b-logs.json | jq '[.[] | select(.severity=="ERROR") | .jsonPayload.trace_id] | unique' > /tmp/error-trace-ids.json

# Find matching events in other services by trace_id
TRACE_IDS=$(cat /tmp/error-trace-ids.json | jq -r '.[]')
for trace_id in $TRACE_IDS; do
  echo "=== Trace: $trace_id ===" >> /tmp/correlated-events.txt
  cat /tmp/service-a-logs.json | jq ".[] | select(.jsonPayload.trace_id==\"$trace_id\")" >> /tmp/correlated-events.txt
  cat /tmp/backend-logs.json | jq ".[] | select(.jsonPayload.trace_id==\"$trace_id\")" >> /tmp/correlated-events.txt
done

Read the full file on GitHub · 331 lines

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. 2mo ago First seen · 331 lines · 48 tokens per session scan A 39c6559cfc8f

Subscribe to this mod's changes

gcp-pattern-finder is an agent published in the GitHub repository eveld/claude (10 stars, last pushed 9mo ago), licensed MIT. It adds 48 tokens to every session and 2,857 once invoked, about $0.0002 per session on Opus 5.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.

Related

gcp-pattern-finder compared with agents from other repositories

gcp-pattern-finder next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
gcp-pattern-findereveld/claudeAgent109mo agoMITA48Claude Code
cloud-architecttravisjneuman/.claudeAgent1072d agoMITA69Claude Code
debugging-specialisttravisjneuman/.claudeAgent1072d agoMITA32Claude Code
performance-optimizertravisjneuman/.claudeAgent1072d agoMITA28Claude Code
serverless-specialisttravisjneuman/.claudeAgent1072d agoMITA72Claude Code
investigatorduthaho/claudekitAgent973mo agoMITA155Claude Code
scoutduthaho/claudekitAgent973mo agoMITA148Claude Code