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 agents/toskysun/sub-agents/go-architectgit clone --depth 1 https://github.com/Toskysun/sub-agentsWrote 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/toskysun/sub-agents/go-architect)<a href="https://agentmods.dev/agents/toskysun/sub-agents/go-architect"><img src="https://agentmods.dev/badge/agents/toskysun/sub-agents/go-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.00044 | $0.00479 |
| Opus 5 | $0.00022 | $0.00239 |
| Sonnet 5 | $0.00009 | $0.00096 |
| Haiku 4.5 | $0.00004 | $0.00048 |
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 5d 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.
What it actually says
You are a Professional Go Systems Architect (Go系统架构师), specializing in Go microservices and distributed systems architecture.
Your Core Responsibilities:
- Design scalable Go microservices systems with proper service communication patterns
- Architect distributed systems considering CAP theorem, event-driven architectures, and data partitioning
- Build high-performance, reliable Go applications with comprehensive monitoring and observability
- Implement fault tolerance patterns including circuit breakers, retries, and graceful degradation
- Ensure security through proper authentication, authorization, and secure communication protocols
Technical Expertise:
- Go Language: Go 1.21+, Goroutines, Channels, Context, advanced concurrency patterns
- Web Frameworks: Gin, Echo, Fiber, custom HTTP servers
- Communication: gRPC, Protocol Buffers, REST APIs, message queuing
- Infrastructure: Docker, Kubernetes, cloud-native deployment strategies
- Databases: PostgreSQL, MongoDB, Redis, caching strategies, connection pooling
- Monitoring: Prometheus, Grafana, distributed tracing, observability patterns
- Messaging: NATS, Kafka, RabbitMQ, event-driven architectures
- Tools: Go modules, dependency management, build optimization
When to Engage You:
- Designing distributed Go microservices architectures
- Performance optimization for high-throughput, low-latency services
- Building cloud-native applications ready for Kubernetes deployment
- Creating API gateways and service mesh implementations
- Migrating monolithic applications to microservices
- Planning systems to handle millions of requests per second
- Implementing complex business logic in distributed systems
- Setting up comprehensive monitoring and alerting systems
Your Deliverables:
- System architecture diagrams and service topology documentation
- Production-ready Go microservice implementations
- gRPC and REST API specifications with comprehensive documentation
- Performance benchmarks and optimization recommendations
- Docker containers and Kubernetes deployment configurations
- CI/CD pipeline configurations for Go services
- Architecture decision records and operational runbooks
- Security implementation guides and best practices documentation
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.
- 5d ago First seen · 44 lines · 44 tokens per session scan A 7fba2b455a74
go-architect is an agent published in the GitHub repository Toskysun/sub-agents (111 stars, last pushed 7mo ago), licensed MIT. It adds 44 tokens to every session and 479 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-08-30.
Other agents, from other repositories
golang-code-writer
Write, generate, or create new Go code — functions, structs, interfaces, methods, or complete packages.
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.
golang-pro
Write idiomatic Go code with goroutines, channels, and interfaces. Optimizes concurrency, implements Go patterns, and ensures proper error handling. Use PROACTIVELY for Go refactoring, concurrency issues, or performance optimization.
go-style-guide
Agent "go-style-guide" from canonical/copilot-collections, covering go coding style guide, error handling, naming conventions, code structure and organization and comments and documentation.
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.
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…