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 niels-emmer/myace --skill gcp-waf-reviewgit clone --depth 1 https://github.com/niels-emmer/myaceWrote 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/niels-emmer/myace/gcp-waf-review)<a href="https://agentmods.dev/skills/niels-emmer/myace/gcp-waf-review"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/gcp-waf-review/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/niels-emmer/myace/gcp-waf-review"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/gcp-waf-review.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.00041 | $0.01003 |
| Opus 5 | $0.00020 | $0.00502 |
| Sonnet 5 | $0.00008 | $0.00201 |
| Haiku 4.5 | $0.00004 | $0.00100 |
Grade A, and why
GCP Architecture Framework Pillar Review 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 9d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
The Google Cloud Architecture Framework is Google Cloud's set of design
principles for building reliable, secure, cost-optimized, operationally
excellent, performant, and sustainable workloads on GCP. This skill is the
GCP-specific companion to iac-expert's generic well-architected-review
skill: it maps each pillar to the concrete GCP services and decisions that
actually move the needle, so a review checks real GCP constructs rather than
abstract principles.
When to use it
Before calling any nontrivial GCP infrastructure change done — new resources, materially changed configuration, anything that affects how the workload is reached, scaled, secured, or paid for. Skip it for genuinely cosmetic changes (a label fix, a variable rename with no resource impact).
The pillars, and what to actually check in GCP
Operational excellence. Can this change be deployed, rolled back, and monitored the same way as the rest of the environment — same pipeline (Cloud Build / GitHub Actions), same alerting (Cloud Monitoring), same logging (Cloud Logging, Cloud Audit Logs)? Is there a way to tell the resource is healthy without logging into the console by hand? Does it run as code (IaC) rather than click-ops, so it's reproducible?
Security, privacy, and compliance. Does this follow private-by-default
networking (no public IPs, VPC firewall rules scoped to least access) and
service-account-over-long-lived-keys? Does it grant any new IAM role, and is
it scoped to least privilege rather than a broad roles/owner/* grant? Does
it introduce or remove a documented exception? Is Security Command Center
posture and Cloud Audit Logs coverage still intact?
Reliability. Does the resource have a single point of failure it didn't have to have? Consider multi-zone deployment (a managed instance group across zones, a regional Cloud SQL/Spanner instance, a global/regional load balancer in front of multiple backends), GCS versioning and object lifecycle for durable data, and Cloud SQL automated backups. If it fails, what notices and how does recovery happen — automatically (Cloud Monitoring alarms, managed instance group autoscaling, Cloud DNS failover) or does someone have to intervene? Does the change affect an existing backup path?
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.
- 9d ago First seen · 88 lines · 41 tokens per session scan A b114f1d74b0f
GCP Architecture Framework Pillar Review is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed 5d ago), licensed MIT. It adds 41 tokens to every session and 1,003 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-09-03.
Other skills, from other repositories
implementing-gcp-organization-policy-constraints
Implement GCP Organization Policy constraints to enforce security guardrails across the entire resource hierarchy, restricting risky configurations and ensuring compliance at organization, folder, and project levels.
Cloud Security & Container Hardening
AWS/Azure/GCP security auditing, container and Kubernetes hardening, Infrastructure as Code scanning, and cloud compliance assessment.
loom-kubernetes
Kubernetes deployment, cluster architecture, security, and operations.
loom-prometheus
Prometheus monitoring and alerting for cloud-native observability.
terraform-infrastructure
Structures, writes, and reviews Terraform infrastructure code. Covers module layout, remote state, workspace strategy, variable and secrets handling, CI plan/apply pipeline, naming conventions, and multi-region deployment patterns (provider aliases, per-region state, failover strategies), while delegating shared risk…
design-aws-terraform-iac
Designs AWS-targeted Terraform infrastructure plans before implementation. Focuses on service selection, module boundaries, state/backends, environment separation, security/compliance guardrails, acceptance criteria, and explicit risk/validation assumptions.