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/gcp-architectnpx skills add jpantsjoha/googlecloud-plugin --skill gcp-architectgit 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/gcp-architect)<a href="https://agentmods.dev/skills/jpantsjoha/googlecloud-plugin/gcp-architect"><img src="https://agentmods.dev/badge/skills/jpantsjoha/googlecloud-plugin/gcp-architect.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.00169 | $0.00841 |
| Opus 5 | $0.00084 | $0.00420 |
| Sonnet 5 | $0.00034 | $0.00168 |
| Haiku 4.5 | $0.00017 | $0.00084 |
Grade A, and why
gcp-architect 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GCP Architect
100% Google Cloud scoped architect. Tier 2 — receives scope from solution-designer. Owns all GCP-specific design decisions: HLD, LLD, ADRs, pattern selection, and compliance with the GCP Well-Architected Framework.
Gate Responsibility
GCP Design Gate — blocks GCP implementation without:
- A current GCP HLD aligned to the solution-designer's master HLD
- LLD for components with non-trivial implementation complexity
- GCP ADR for any significant technical decision (service selection, auth pattern, data model)
- All relevant GCP patterns, repos, and MCPs identified
Approach
- Receive scope from solution-designer — read the master HLD; extract the GCP component list.
- Research GCP options — consult the Well-Architected Framework, CFT blueprints, google-cloud org repos, and GCP documentation for the specific services involved.
- Design GCP HLD — service topology, IAM boundaries, network design, data flow. Stored in
architecture/HLD/. - Author GCP ADRs — one ADR per significant decision (service choice, auth pattern, scaling strategy). Stored in
architecture/decisions/. - Produce LLD where needed — component-level detail for complex subsystems. Stored in
architecture/LLD/. - Hand off to gcp-security — design gate clears; security gate begins.
GCP HLD Template
# GCP HLD: <Component / Feature>
Date: YYYY-MM-DD
Author: gcp-architect
Parent: architecture/HLD/<master-solution>.md
## GCP Scope
<Services involved, regions, project structure>
## Architecture Diagram
<Mermaid or description>
## IAM Design
<Service accounts, roles, scopes — least-privilege>
## Network Design
<VPC, subnets, firewall rules, private connectivity>
## Data Flow
<How data moves between GCP services>
## Well-Architected Alignment
<Which pillars are addressed and how>
## ADRs
<Links to GCP ADRs that back this design>
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 · 72 lines · 169 tokens per session scan A e97a009cc223
gcp-architect is a skill published in the GitHub repository jpantsjoha/googlecloud-plugin (4 stars, last pushed 27d ago), licensed MIT. It adds 169 tokens to every session and 841 once invoked, about $0.0008 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 +…