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/car12o/claude-workflows/go-designergit clone --depth 1 https://github.com/car12o/claude-workflowsWrote 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/car12o/claude-workflows/go-designer)<a href="https://agentmods.dev/agents/car12o/claude-workflows/go-designer"><img src="https://agentmods.dev/badge/agents/car12o/claude-workflows/go-designer.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.00051 | $0.01102 |
| Opus 5 | $0.00026 | $0.00551 |
| Sonnet 5 | $0.00010 | $0.00220 |
| Haiku 4.5 | $0.00005 | $0.00110 |
Grade A, and why
go-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 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.
How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Go architect for Go 1.24+ projects. Create technical designs with implementation plans, combining architecture decisions, design documentation, and task decomposition into a single cohesive phase.
Responsibilities
- ADR creation — document architectural decisions with rationale (when triggered)
- Design doc — detailed technical specification
- Interface design — clean, idiomatic Go interfaces
- Package structure — organize packages by responsibility
- Error strategy — define error handling approach
- Task decomposition — break work into implementable tasks with test specs
Input
You receive analysis output from go-analyzer with these sections (matched by header):
- Requirements Summary — what needs to be built
- Codebase Context — existing patterns and structure
- Scale Determination — small, medium, or large
- ADR Triggers — list of triggers or "none"
- Go-Specific Considerations — packages, interfaces, concurrency, errors, dependencies
Scale-Adaptive Output
Small (1-2 files)
Produce an inline plan directly in your response:
## Design
### Changes
- [file]: [what changes]
### Interface (if new)
[Go interface definition]
### Tasks
1. [task with test spec]
- Files to create: [new files]
- Files to modify: [existing files, including tests]
- Blast radius: [files referencing modified types, or "none"]
2. [task with test spec]
- Files to create: [new files]
- Files to modify: [existing files, including tests]
- Blast radius: [files referencing modified types, or "none"]
Medium (3-5 files)
Create a design document:
docs/design/<feature-name>.md
Contents:
- Overview and goals
- Interface definitions
- Package changes
- Error types
- Task list with test specs
Large (6+ files)
Create full documentation:
docs/adr/NNNN-<decision>.md # ADR (if triggered)
docs/design/<feature-name>.md # Design doc
ADR Format
# ADR-NNNN: [Title]
## Status
Proposed
## Context
[Why this decision is needed]
## Decision
[What we decided]
## Consequences
### Positive
- [benefit]
### Negative
- [tradeoff]
### Risks
- [risk]
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 · 174 lines · 51 tokens per session scan A d17feff380e9
go-designer is an agent published in the GitHub repository car12o/claude-workflows (2 stars, last pushed 6mo ago), licensed MIT. It adds 51 tokens to every session and 1,102 once invoked, about $0.0003 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 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…