role-go-engineer

role-go-engineer is a skill for Claude Code from saemihemma/lead-producer-oss. It costs 33 tokens per session (578 once invoked), scanned A, original, MIT.

A code-review guide for Go, a programming language commonly used for services and command-line tools.

In plain words
What is it for?
Use it when reviewing or writing Go to check idiomatic code, contextual error wrapping, cancellation and shutdown, small interfaces, race-detector tests, coverage, and benchmarks.
Why use it?
It helps find unclear error handling, unsafe concurrency, leaking goroutines, overly large interfaces, formatting issues, and missing tests.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it when reviewing or writing Go to check idiomatic code, contextual error wrapping, cancellation and shutdown, small interfaces, race-detector tests, coverage, and benchmarks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/saemihemma/lead-producer-oss/role-go-engineer
Install

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.

Any agent
npx skills add saemihemma/lead-producer-oss --skill role-go-engineer
Clone the repo
git clone --depth 1 https://github.com/saemihemma/lead-producer-oss

Made for: Claude Code.

Wrote 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.

agentmods badge for role-go-engineer

README.md
[![agentmods](https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/role-go-engineer/github.svg)](https://agentmods.dev/skills/saemihemma/lead-producer-oss/role-go-engineer)
Your own site
<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/role-go-engineer"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/role-go-engineer/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.

agentmods 80×15 button for role-go-engineer

Your own site · 80×15
<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/role-go-engineer"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/role-go-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 578 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.00578
Opus 5 $0.00016 $0.00289
Sonnet 5 $0.00007 $0.00116
Haiku 4.5 $0.00003 $0.00058

Measured 10d ago against content hash 92563c2ec159, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

role-go-engineer 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 10d 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.

.claude/skills/role-go-engineer/SKILL.md · 63 lines

How it starts

The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Go Engineer

Use When

  • Reviewing or writing Go code
  • Assessing concurrency safety, error handling, or interface design
  • Evaluating test coverage or benchmark quality

Do NOT Use When

  • Problem is architecture-level, not language-level
  • Code is a different language using Go-like patterns

What You Own

  • Idiomatic Go enforcement (simplicity over cleverness)
  • Error handling: wrapping, context, custom types
  • Concurrency safety: goroutine lifecycle, channel discipline, context cancellation
  • Interface design: small, consumer-defined
  • Test quality and race detection

Working Method

  1. Run gofmt/goimports compliance check.
  2. Verify error handling: all errors wrapped with context via fmt.Errorf("context: %w", err).
  3. Check concurrency: goroutine leaks, context propagation, proper shutdown.
  4. Inspect interfaces: small (1-3 methods), defined where consumed.
  5. Verify tests run with -race flag and coverage is adequate.
  6. Produce verdict with highest-risk issues first.

Key Idioms

  • Accept interfaces, return structs
  • Errors are values — wrap with context, use errors.Is/errors.As
  • Prefer table-driven tests with subtests
  • Use context.Context for cancellation and deadlines
  • Preallocate slices when size is known (make([]T, 0, n))
  • Use sync.Pool for frequently allocated objects
  • Avoid init() — prefer explicit initialization
  • Use errgroup for concurrent operations with error collection
  • Functional options pattern for flexible constructors

Testing Standards

  • Framework: standard go test with table-driven subtests
  • Race detection: always go test -race ./...
  • Coverage: go test -cover ./... with -coverprofile for CI
  • Benchmarks: func BenchmarkX(b *testing.B) for performance-critical paths
  • Fuzzing: go test -fuzz (Go 1.18+) for input validation

Default Output

GO REVIEW
=========
Idioms: gofmt compliance, error handling, interface design
Safety: concurrency, goroutine lifecycle, race conditions
Quality Risks: error swallowing, goroutine leaks, missing tests
Recommendation: highest-leverage fixes

Read the full file on GitHub · 63 lines

Changes

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.

  1. 10d ago First seen · 63 lines · 33 tokens per session scan A 92563c2ec159

Subscribe to this mod's changes

role-go-engineer is a skill published in the GitHub repository saemihemma/lead-producer-oss (2 stars, last pushed 7d ago), licensed MIT. It adds 33 tokens to every session and 578 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.