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.
git clone --depth 1 https://github.com/eveld/claudeWrote 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/agents/eveld/claude/gcp-pattern-finder)<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.
<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>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.00048 | $0.02857 |
| Opus 5.5 | $0.00019 | $0.01143 |
| Sonnet 5.5 | $0.00010 | $0.00571 |
| Haiku 4.5 | $0.00005 | $0.00286 |
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.
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
-
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
-
Detect Patterns and Trends
- Find recurring error sequences
- Identify common failure modes
- Detect cascade failures
- Discover temporal patterns (time-of-day, deployment-related)
-
Analyze Service Relationships
- Map upstream/downstream dependencies
- Identify bottlenecks and slow services
- Find services impacted by failures
- Discover hidden dependencies
-
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
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.
- 2mo ago First seen · 331 lines · 48 tokens per session scan A 39c6559cfc8f
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.
gcp-pattern-finder compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| gcp-pattern-findereveld/claude | Agent | 10 | 9mo ago | MIT | A | 48 | Claude Code |
| cloud-architecttravisjneuman/.claude | Agent | 107 | 2d ago | MIT | A | 69 | Claude Code |
| debugging-specialisttravisjneuman/.claude | Agent | 107 | 2d ago | MIT | A | 32 | Claude Code |
| performance-optimizertravisjneuman/.claude | Agent | 107 | 2d ago | MIT | A | 28 | Claude Code |
| serverless-specialisttravisjneuman/.claude | Agent | 107 | 2d ago | MIT | A | 72 | Claude Code |
| investigatorduthaho/claudekit | Agent | 97 | 3mo ago | MIT | A | 155 | Claude Code |
| scoutduthaho/claudekit | Agent | 97 | 3mo ago | MIT | A | 148 | Claude Code |