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 skills/jpantsjoha/googlecloud-plugin/well-architectednpx skills add jpantsjoha/googlecloud-plugin --skill well-architectedgit clone --depth 1 https://github.com/jpantsjoha/googlecloud-pluginWrote 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/jpantsjoha/googlecloud-plugin/well-architected)<a href="https://agentmods.dev/skills/jpantsjoha/googlecloud-plugin/well-architected"><img src="https://agentmods.dev/badge/skills/jpantsjoha/googlecloud-plugin/well-architected.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.00082 | $0.00726 |
| Opus 5 | $0.00041 | $0.00363 |
| Sonnet 5 | $0.00016 | $0.00145 |
| Haiku 4.5 | $0.00008 | $0.00073 |
Grade A, and why
well-architected 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GCP Well-Architected Framework
Six pillars that every GCP workload should be evaluated against. Referenced in every HLD, security review, and operational readiness check.
The Six Pillars
| Pillar | Core Question | Key Practices |
|---|---|---|
| Operational Excellence | Can we build, run, and evolve the system reliably? | IaC, CI/CD, runbooks, monitoring-as-code |
| Security | Is the system protected against threats? | Least-privilege IAM, encryption, no public exposure by default |
| Reliability | Will the system recover from failures? | Multi-region, health checks, SLOs, chaos testing |
| Cost Optimization | Are we spending efficiently? | Right-sizing, committed use, lifecycle policies, budget alerts |
| Performance | Can the system handle load and scale? | Autoscaling, CDN, caching, regional proximity |
| Sustainability | Are we minimizing environmental impact? | Carbon-aware regions, efficient resource use |
Quick Review Checklist (per design)
Operational Excellence
- Infrastructure as Code (Terraform or Config Connector)
- CI/CD pipeline with automated tests
- Runbook for each primary failure mode
- Alerting tied to SLOs
Security
- Least-privilege IAM throughout
- No public exposure without intent
- Secrets in Secret Manager
- Network deny-by-default
Reliability
- SLO defined (availability + latency)
- Health checks configured
- Multi-zone or multi-region for production
- Backup and recovery tested
Cost Optimization
- Right-sized instances (use GCP recommender)
- Committed use discounts evaluated
- Budget alerts configured
- Lifecycle policies on storage
Performance
- Load tested at target traffic
- Caching layer evaluated
- CDN for static assets
- Autoscaling configured
Sustainability
- Low-carbon region selected where latency allows
- Idle resources scheduled for shutdown
References
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 70 lines · 82 tokens per session scan A 6e190b411a94
well-architected is a skill published in the GitHub repository jpantsjoha/googlecloud-plugin (4 stars, last pushed 27d ago), licensed MIT. It adds 82 tokens to every session and 726 once invoked, about $0.0004 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 skills, from other repositories
cli-backup-sync
Backup and restore OmniRoute data from the CLI. Trigger incremental snapshots, sync to cloud storage, manage backup schedules, and restore from archive files.
omni-sync-cloud
Synchronise OmniRoute configuration, provider connections, and settings to/from cloud storage. Manage cloud worker authentication and remote backup targets.
cli-tunnel
Start and stop tunnel connections (ngrok, Cloudflare, custom) from the CLI. Inspect active tunnel URLs, configure authentication, and test external reachability.
aegisops-ai
Autonomous DevSecOps & FinOps Guardrails. Orchestrates Gemini 3 Flash to audit Linux Kernel patches, Terraform cost drifts, and K8s compliance.
omni-tunnels
Create and manage secure tunnels (ngrok, Cloudflare Tunnel, custom) to expose OmniRoute to the internet or share access with remote agents and CI pipelines.
ak-dev-architecture
Agent Kernel architectural principles, core abstractions, and design patterns. Use this skill when you need to understand the codebase structure, how components interact, or before making changes to core functionality. Covers Session, Agent, Runner, Module, Runtime, AgentService, ChatService (execution core +…