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 trilwu/secskills --skill investigating-gcp-incidentsgit clone --depth 1 https://github.com/trilwu/secskillsWrote 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/trilwu/secskills/investigating-gcp-incidents)<a href="https://agentmods.dev/skills/trilwu/secskills/investigating-gcp-incidents"><img src="https://agentmods.dev/badge/skills/trilwu/secskills/investigating-gcp-incidents/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/skills/trilwu/secskills/investigating-gcp-incidents"><img src="https://agentmods.dev/badge/skills/trilwu/secskills/investigating-gcp-incidents.svg" alt="Reviewed on agentmods" width="80" 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.00098 | $0.01980 |
| Opus 5 | $0.00049 | $0.00990 |
| Sonnet 5 | $0.00020 | $0.00396 |
| Haiku 4.5 | $0.00010 | $0.00198 |
Grade A, and why
investigating-gcp-incidents scanned grade A with 1 finding 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 13d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sL "https://defuddle.md/<url>" # scheme in the path is optional How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Investigating GCP Incidents
The completeness of a GCP investigation is decided before the incident, by which audit logs were enabled. The single most damaging mistake is reading an empty query result as "nothing happened" when the real answer is "that log category was never turned on." Establish visibility first; conclude second.
GCP's audit model is not AWS's and not Azure's. Two categories are always on and two are mostly off, and knowing which is which is the difference between a scoped investigation and a false all-clear.
When to Use
- Responding to a suspected compromise in a GCP project or organization
- Investigating a leaked or abused service-account key
- Working a Security Command Center, Event Threat Detection, or Chronicle alert
- Reconstructing a principal's activity across projects
- Scoping IAM policy or resource changes after a suspected privilege escalation
When NOT to Use
- The incident is in AWS — use
investigating-aws-incidents; in Azure or Microsoft 365 / Entra — useinvestigating-azure-incidentsorinvestigating-m365-entra - Attacking GCP rather than investigating it — use
exploiting-cloud-platforms - A GKE cluster compromise specifically — start here for the cloud-plane
view, then use
defending-kubernetesfor the cluster-plane - Deciding whether an alert is even an incident — use
triaging-security-alertsfirst
Establish Visibility Before You Conclude
GCP Cloud Audit Logs come in four streams, and their defaults are the whole game:
| Stream | Default | Can disable? | What it captures |
|---|---|---|---|
| Admin Activity | Always on | No — written even if the Logging API is disabled | Config and metadata writes: IAM changes, resource create/delete |
| System Event | Always on | No | Google-initiated actions on your resources |
| Data Access | Off (except BigQuery) | Yes | Reads and data-plane access — who read the bucket, the secret, the dataset |
| Policy Denied | On | No (can exclude from storage) | Access blocked by policy — VPC-SC, org policy |
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.
- 13d ago First seen · 172 lines · 98 tokens per session scan A 784e866d4ac6
investigating-gcp-incidents is a skill published in the GitHub repository trilwu/secskills (138 stars, last pushed 8d ago), licensed MIT. It adds 98 tokens to every session and 1,980 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agent-platform-tuning
Agent Platform Model Tuning. Use when you need to fine-tune open models or Gemini models using Agent Platform infrastructure. Don't use for model training outside Agent Platform, model deployment to endpoints (use agent-platform-deploy), or managing serving endpoints (use agent-platform-endpoint-management).
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-alert-configuration
Configures alerting policies in Terraform for Google Kubernetes Engine (GKE) clusters, workloads, and services using PromQL and Google Cloud Managed Service for Prometheus. Use when writing, analyzing, validating, or deploying Terraform alerting policies to monitor GKE service latency, traffic, error rates using…
google-cloud-solution-n-tier-serverless-web-app
Assists in designing and implementing secure n-tier serverless web applications and microservices on Google Cloud. Use when users need architecture designs, security checklists, Terraform code, or deployment guidance for multi-tier serverless apps, regional data residency / European sovereignty compliance, zero-trust…
application-design-center-design-deploy
Processes GCP infrastructure design and deployment workflows within Application Design Center (ADC). Use when: - Designing GCP infrastructure with Terraform. - Validating local HCL. - Performing best-practice plan scans. - Importing templates to Application Design Center (ADC). - Deploying templates. - Troubleshooting…
cloud-run-basics
Manages Cloud Run services, jobs, and worker pools. Use when you need to deploy applications responding to HTTP requests (services), run event-triggered or scheduled tasks (jobs), or handle always-on pull-based background processing (worker pools).