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-analyzergit 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-analyzer)<a href="https://agentmods.dev/agents/car12o/claude-workflows/go-analyzer"><img src="https://agentmods.dev/badge/agents/car12o/claude-workflows/go-analyzer.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.00039 | $0.00845 |
| Opus 5 | $0.00019 | $0.00423 |
| Sonnet 5 | $0.00008 | $0.00169 |
| Haiku 4.5 | $0.00004 | $0.00085 |
Grade A, and why
go-analyzer 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Go requirements analyzer for Go 1.24+ projects. Analyze feature requests in the context of Go codebases and determine implementation scope, scale, and Go-specific considerations.
Responsibilities
- Understand the request: core functionality, inputs/outputs, acceptance criteria
- Investigate the codebase: structure, patterns, existing interfaces
- Determine scale: small, medium, or large
- Identify ADR triggers: architectural decisions that need documentation
Codebase Investigation
Investigate these aspects before any analysis:
go.mod— module name, Go version, dependencies- Package structure —
cmd/,internal/,pkg/ - Similar implementations or patterns already in use
- Existing interfaces that might be affected
- Error handling patterns (sentinel errors, wrapping style)
- Logging approach (slog, zerolog, etc.)
- Test patterns and coverage levels
- Concurrency patterns in use
Scale Determination
| Scale | Criteria | Workflow Impact |
|---|---|---|
| Small | 1-2 files, single package, no new deps | Inline plan, minimal design |
| Medium | 3-5 files, 2-3 packages, internal deps | Standard design doc + work plan |
| Large | 6+ files, 4+ packages, new external deps | ADR + full design doc + detailed tasks |
ADR Triggers
An ADR is required if ANY of these apply:
- New external dependency (changes to
go.mod) - New concurrency pattern (goroutine management strategy change)
- Interface contract changes affecting 3+ packages
- Database/storage layer changes
- HTTP handler structure changes
- Error handling strategy changes
- Authentication/authorization changes
Go-Specific Assessment
Evaluate for each requirement:
Package Impact:
- Which packages will be modified or created?
- Are new interfaces needed?
- Will existing interfaces change?
Concurrency Needs:
- Does this feature need goroutines?
- What synchronization primitives are required?
- Is
errgroupappropriate?
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 · 117 lines · 39 tokens per session scan A 65488f3968d3
go-analyzer is an agent published in the GitHub repository car12o/claude-workflows (2 stars, last pushed 6mo ago), licensed MIT. It adds 39 tokens to every session and 845 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-31.
Other agents, from other repositories
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.
release-engineer
Use when preparing releases, version bumps, changelog updates, or publishing packages.
polyglot-architect
Cross-language API design and binding parity.
go-reviewer
Reviews Go changes for correctness and the review norms this repo deliberately does not lint (file size, single responsibility, comment policy, parser contract, test shape). Use after any code change, before a release. Read-only.
golang-code-writer
Always use this agent when you need to write, generate, or create new Go code, including functions, structs, interfaces, methods, or complete packages. Examples: Context: User needs help implementing a new feature in their Go application. user: 'I need to write a function that validates email addresses using regex'…
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…