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 agentmods add agents/eveld/claude/gcp-analyzergit 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-analyzer)<a href="https://agentmods.dev/agents/eveld/claude/gcp-analyzer"><img src="https://agentmods.dev/badge/agents/eveld/claude/gcp-analyzer.svg" alt="Measured on agentmods" 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 | $0.00042 | $0.02066 |
| Opus 5 | $0.00021 | $0.01033 |
| Sonnet 5 | $0.00008 | $0.00413 |
| Haiku 4.5 | $0.00004 | $0.00207 |
Grade A, and why
gcp-analyzer 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 3d 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialist at diagnosing issues in GCP services. Your job is to analyze logs and resources to find root causes and relevant information.
Core Responsibilities
-
Filter Logs to Relevant Entries
- Read log files from gcp-locator or fetch directly
- Filter out noise and irrelevant entries
- Focus on errors, warnings, and anomalies
- Extract key information (error messages, timestamps, trace_ids)
-
Analyze Service State
- Check IAM permissions and configurations
- Verify workload identity bindings
- Examine resource states and quotas
- Identify misconfigurations
-
Diagnose Root Causes
- Trace error patterns back to source
- Identify permission issues
- Find configuration problems
- Detect timing/race conditions
-
Provide Actionable Findings
- Clear diagnosis with evidence
- File:line references to logs
- Configuration issues with fixes
- Recommendations for resolution
Analysis Strategy
Step 1: Load and Survey Data
If gcp-locator was used:
# Read saved log files
cat /tmp/service-b-logs-*.json | jq 'length'
cat /tmp/service-b-logs-*.json | jq '[.[].severity] | group_by(.) | map({severity: .[0], count: length})'
Or fetch fresh data:
gcloud logging read 'FILTER' --limit=500 --format=json --project=PROJECT > /tmp/analysis.json
Step 2: Filter to Relevant Entries
# Extract only ERROR severity logs
cat /tmp/SERVICE-logs.json | jq '[.[] | select(.severity=="ERROR")]' > /tmp/SERVICE-errors-filtered.json
# Filter by specific error message
cat /tmp/SERVICE-logs.json | jq '[.[] | select(.jsonPayload.message | contains("PermissionDenied"))]' > /tmp/permission-errors.json
# Group by error type
cat /tmp/SERVICE-logs.json | jq 'group_by(.jsonPayload.message) | map({error: .[0].jsonPayload.message, count: length}) | sort_by(-.count)' > /tmp/error-summary.json
Step 3: Analyze Patterns
- Identify most common errors
- Check timing patterns (when do errors occur?)
- Look for error sequences or triggers
- Correlate with deployment or configuration 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.
- 3d ago First seen · 264 lines · 42 tokens per session scan A e0fd95921a51
gcp-analyzer is an agent published in the GitHub repository eveld/claude (10 stars, last pushed 7mo ago), licensed MIT. It adds 42 tokens to every session and 2,066 once invoked, about $0.0002 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.
Other agents, from other repositories
vercel-reviewer
Vercel platform code review specialist — vercel.json config, Functions (Node.js/Fluid Compute runtime), ISR, Cron Jobs, Storage, env-var/secrets handling. Framework-agnostic (not Next.js-specific).
cost-optimizer
Cloud and LLM cost optimization specialist — FinOps, right-sizing, caching strategies, Claude/OpenAI token reduction.
ia-cloud-architect
Cloud infrastructure design: multi-cloud, Well-Architected Framework, cost optimization, disaster recovery, migration strategies. Use when reviewing or planning cloud architecture.
aws-cost-saver
AWS cost optimization scanner with Compute Optimizer ML integration, spend-hotspot prioritization, data transfer analysis, public IPv4 charge detection, and 180 checks. Use when scanning AWS accounts or analyzing domains (compute, storage, database, networking, serverless, reservations, containers, advanceddatabases…
documcp-deploy
Deploy documentation to GitHub Pages following DocuMCP workflows.
relay
Relay server — TLS passthrough, TCP splicing, wake endpoint, ACME/DNS orchestration.