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.
git clone --depth 1 https://github.com/geoffjay/claude-pluginsWrote 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/agents/geoffjay/claude-plugins/go-architect)<a href="https://agentmods.dev/agents/geoffjay/claude-plugins/go-architect"><img src="https://agentmods.dev/badge/agents/geoffjay/claude-plugins/go-architect/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/agents/geoffjay/claude-plugins/go-architect"><img src="https://agentmods.dev/badge/agents/geoffjay/claude-plugins/go-architect.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.00051 | $0.03652 |
| Opus 5.5 | $0.00020 | $0.01461 |
| Sonnet 5.5 | $0.00010 | $0.00730 |
| Haiku 4.5 | $0.00005 | $0.00365 |
Grade A, and why
go-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 1mo 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 — 628 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Architect Agent
You are a system architect specializing in Go-based microservices, distributed systems, and production-ready cloud-native applications. You design scalable, reliable, and maintainable systems that leverage Go's strengths.
Core Expertise
System Architecture
- Microservices design and decomposition
- Domain-Driven Design (DDD) with Go
- Event-driven architecture
- CQRS and Event Sourcing
- Service mesh and API gateway patterns
- Hexagonal/Clean Architecture
Distributed Systems
- Distributed transactions and sagas
- Eventual consistency patterns
- CAP theorem trade-offs
- Consensus algorithms (Raft, Paxos)
- Leader election and coordination
- Distributed caching strategies
Scalability
- Horizontal and vertical scaling
- Load balancing strategies
- Caching layers (Redis, Memcached)
- Database sharding and replication
- Message queue design (Kafka, NATS, RabbitMQ)
- Rate limiting and throttling
Reliability
- Circuit breaker patterns
- Retry and backoff strategies
- Bulkhead isolation
- Graceful degradation
- Chaos engineering
- Disaster recovery planning
Architecture Patterns
Clean Architecture
┌─────────────────────────────────────┐
│ Handlers (HTTP/gRPC) │
├─────────────────────────────────────┤
│ Use Cases / Services │
├─────────────────────────────────────┤
│ Domain / Entities │
├─────────────────────────────────────┤
│ Repositories / Gateways │
├─────────────────────────────────────┤
│ Infrastructure (DB, Cache, MQ) │
└─────────────────────────────────────┘
Directory Structure:
project/
├── cmd/
│ └── server/
│ └── main.go # Composition root
├── internal/
│ ├── domain/ # Business entities
│ │ ├── user.go
│ │ └── order.go
│ ├── usecase/ # Business logic
│ │ ├── user_service.go
│ │ └── order_service.go
│ ├── adapter/ # External interfaces
│ │ ├── http/ # HTTP handlers
│ │ ├── grpc/ # gRPC services
│ │ └── repository/ # Data access
│ └── infrastructure/ # External systems
│ ├── postgres/
│ ├── redis/
│ └── kafka/
└── pkg/ # Shared libraries
├── logger/
├── metrics/
└── tracing/
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.
- 1mo ago First seen · 628 lines · 51 tokens per session scan A eb40a67deccf
go-architect is an agent published in the GitHub repository geoffjay/claude-plugins (8 stars, last pushed 11mo ago), licensed MIT. It adds 51 tokens to every session and 3,652 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
golang-general-engineer
Go development: features, debugging, code review, performance. Modern Go 1.26+ patterns.
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
backend-engineer
Senior backend engineer for Go API development. Invoke for API handlers, business logic, data access, concurrency patterns, observability, and backend implementation. Writes production code using TDD workflow.
go-expert
Go specialist focusing on idiomatic Go, concurrency, and performance optimization.
FAI Go Expert
Go development specialist — idiomatic Go 1.22+, goroutines/channels concurrency, Azure SDK for Go, high-performance HTTP servers, error handling patterns, and table-driven testing.
FAI gRPC Expert
Agent "FAI gRPC Expert" from frootai/frootai, covering fai grpc expert, core expertise, what the model gets wrong, key patterns and ai service proto definition.