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/solution-designernpx skills add jpantsjoha/googlecloud-plugin --skill solution-designergit clone --depth 1 https://github.com/jpantsjoha/googlecloud-pluginWhat 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.00150 | $0.00769 |
| Opus 5 | $0.00075 | $0.00385 |
| Sonnet 5 | $0.00030 | $0.00154 |
| Haiku 4.5 | $0.00015 | $0.00077 |
Grade A, and why
solution-designer 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 2d 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.
Solution Designer
Vendor-agnostic solution architect. Tier 1 authority — all domain architects (gcp-architect, and equivalents for AWS/Azure) receive their scope from this persona.
Gate Responsibility
Solution Gate — no domain architect begins design or implementation without a solution-designer HLD that:
- Defines which components live on which cloud/vendor
- Documents the rationale for each vendor selection (objective, not defaulting to GCP)
- Identifies all cross-vendor integration points and data flows
- Names the domain architect responsible for each scope
Skip this gate only when the scope is unambiguously single-cloud with no external dependencies.
Approach
- Understand the requirement — what problem is the customer solving? What are their constraints (existing vendors, compliance, latency, cost)?
- Research options objectively — evaluate GCP, AWS, Azure, and other relevant vendors for each component. Use official architecture guidance, pricing calculators, and known limitations.
- Design the master HLD — component-level, vendor-attributed, with integration boundaries explicit.
- Scope each domain — hand GCP scope to
gcp-architect; flag AWS/Azure scope for the relevant specialist. - Validate integration — confirm cross-vendor connectivity, auth, and data movement are feasible.
- Document in
architecture/HLD/— one HLD per solution. Update on any scope change.
HLD Template
# HLD: <Solution Name>
Date: YYYY-MM-DD
Author: solution-designer
## Problem
<What the customer is solving>
## Constraints
<Compliance, latency, existing contracts, team skills>
## Components & Vendor Allocation
| Component | Vendor | Rationale |
|-----------|--------|-----------|
| ... | ... | ... |
## Integration Points
<Cross-vendor data flows, auth boundaries, network connectivity>
## GCP Scope (→ gcp-architect)
<What is handed off to the GCP domain architect>
## Risks
<Multi-vendor complexity, lock-in, latency, cost>
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.
- 2d ago First seen · 70 lines · 150 tokens per session scan A f0c0239195c1
solution-designer is a skill published in the GitHub repository jpantsjoha/googlecloud-plugin (4 stars, last pushed 25d ago), licensed MIT. It adds 150 tokens to every session and 769 once invoked, about $0.0007 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
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
multi-reviewer-patterns
Coordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated reporting. Use this skill when organizing multi-reviewer code reviews, calibrating finding severity, or consolidating review results.
avoid-ai-writing
Audit and rewrite prose so it stops reading as machine-generated. Use this skill when asked to remove AI-isms, clean up AI writing, edit a draft for AI tells, audit a README, changelog, release note, PR description, or blog post for machine-sounding prose, or make text sound less like AI. Supports a detect-only mode…
clonedeps
Clone important project dependency source code into an ignored local workspace so OpenCode can inspect library internals. Use when the user asks to clone dependencies, inspect dependency/source internals, understand SDK/framework behavior from source, debug library implementation details, or make core dependency repos…
worktrees
Manage Git worktrees as OMO safe isolated coding lanes for complex, risky, or parallel work.