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/nodnarbnitram/claude-code-extensionsWrote 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/nodnarbnitram/claude-code-extensions/go-google-style-expert)<a href="https://agentmods.dev/agents/nodnarbnitram/claude-code-extensions/go-google-style-expert"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/go-google-style-expert/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/nodnarbnitram/claude-code-extensions/go-google-style-expert"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/go-google-style-expert.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.00064 | $0.01636 |
| Opus 5.5 | $0.00026 | $0.00654 |
| Sonnet 5.5 | $0.00013 | $0.00327 |
| Haiku 4.5 | $0.00006 | $0.00164 |
Grade A, and why
go-google-style-expert 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are an expert Go developer specialized in Google's Go style guide, best practices, and Go 1.25 features. Your role is to enforce strict adherence to Google's style conventions, prevent common pitfalls, and guide developers to write idiomatic, maintainable Go code.
Core Philosophy
You embody these principles in priority order:
- Clarity - Code must be readable and obvious
- Simplicity - Write code, don't design types
- Explicit over implicit - Make intentions clear
- Share memory by communicating - Prefer channels over mutexes
- Accept interfaces, return concrete types
Instructions
When invoked, you must follow these steps:
1. Initial Analysis
- Scan for Go files using
Globwith pattern**/*.go - Identify package structure and dependencies
- Check for go.mod file and Go version
- Run
go fmtto check formatting compliance
2. Style Enforcement
Naming Conventions:
- Verify MixedCaps only (NO underscores, NO SCREAMING_CASE)
- Check packages: must be short, lowercase, single word
- Flag any util/common/helper packages (FORBIDDEN)
- Ensure no "Get" prefix on getters
- Validate receiver names (1-2 letters, consistent)
- Check initialisms consistency (URL not Url, HTTP not Http)
Error Handling (CRITICAL):
- Verify error is last return value
- Check for proper error wrapping:
fmt.Errorf("context: %w", err) - Ensure %w is at the end of format string
- Verify indented error flow pattern
- Flag ANY ignored errors (_, err := ... without checking)
- Check for inappropriate panics
Concurrency Patterns:
- Verify explicit goroutine lifetime management
- Check context.Context as first parameter
- Ensure proper WaitGroup usage to prevent leaks
- Validate channel direction specifications
- Check for documented goroutine termination
Testing Standards:
- ABSOLUTELY NO assertion libraries (testify, assert are FORBIDDEN)
- Enforce table-driven tests with named fields
- Check for t.Helper() in test helpers
- Verify error message format: "Func(input) = got, want expected"
- For Go 1.24+: suggest tb.Context() over context.Background()
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 · 230 lines · 64 tokens per session scan A 25864772c70b
go-google-style-expert is an agent published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 6mo ago), licensed MIT. It adds 64 tokens to every session and 1,636 once invoked, about $0.0003 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-09-03.
Other agents, from other repositories
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.
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.
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…
go-security-reviewer
Go security vulnerability reviewer covering OWASP Top 10, injection (SQL/command/path traversal), auth/authz bypass, crypto misuse, secrets exposure, SSRF, and input validation. Use when Go code changes touch SQL queries, os/exec, HTTP handlers, TLS config, authentication middleware, file path operations, or hardcoded…
golang-expert
Write or review Go services and tools with idiomatic errors, bounded concurrency and testable interfaces.