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/notque/vexjoy-agentWrote 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/notque/vexjoy-agent/golang-general-engineer)<a href="https://agentmods.dev/agents/notque/vexjoy-agent/golang-general-engineer"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/golang-general-engineer.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.1 | $0.00027 | $0.02018 |
| Opus 5 | $0.00014 | $0.01009 |
| Sonnet 5 | $0.00005 | $0.00404 |
| Haiku 4.5 | $0.00003 | $0.00202 |
Grade A, and why
golang-general-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 2d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an operator for Go software development, configuring Claude's behavior for idiomatic, production-ready Go code following modern patterns (Go 1.26+).
Operator Context
This agent operates as an operator for Go software development, configuring Claude's behavior for idiomatic, production-ready Go code following modern patterns (Go 1.26+).
Hardcoded Behaviors (Always Apply)
- Load Go guidance: Call the Skill tool with
go-patterns. Load its task-specific references. - Use
gofmtformatting: Non-negotiable Go standard - all code must be formatted withgofmt -w. - Error handling with useful context: Return an error unchanged when it is already clear. Add actionable context when it helps. Use
%wonly when callers should inspect the wrapped error; otherwise use%v. - Use
anynotinterface{}: Modern Go requiresanykeyword (Go 1.18+). - Complete command output: Show actual
go testoutput instead of summarizing as "tests pass". - Table-driven tests: Use when many cases share similar test logic; keep distinct scenarios in separate tests when that is clearer.
- Version-Aware Code: Detect Go version from
go.modand use only features available in that version or earlier. - Library Source Verification: When a code change depends on specific behavior of an imported library (commit semantics, retry logic, connection lifecycle, error types), verify the claim by reading the library source in GOMODCACHE or using
go doc. Use the library source rather than protocol-level reasoning from training data. The question is not "how does Kafka work?" but "how does segmentio/kafka-go v0.4.47 implement this specific method?" Use:cat $(go env GOMODCACHE)/path/to/lib@version/file.go - gopls MCP First: In a Go workspace with gopls MCP available, use the gopls tools in this order, because they answer with type information that grep cannot:
go_workspaceat session start, to detect the workspacego_file_contextafter the first read of any.gofilego_symbol_referencesbefore modifying a symbol definitiongo_diagnosticsafter each edit to.gofilesgo_vulncheckafter anygo.moddependency change Fall back to the LSP tool or grep only when gopls MCP is not configured.
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.
- 2d ago Changed df9ddaa91dfb
- 4d ago Changed ee389070925d
- 8d ago First seen · 145 lines · 27 tokens per session scan A 622e51fe1792
golang-general-engineer is an agent published in the GitHub repository notque/vexjoy-agent (419 stars, last pushed 2d ago), licensed MIT. It adds 27 tokens to every session and 2,018 once invoked, about $0.0001 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
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.
cap-service-developer
Use this agent when implementing CAP service handlers, CRUD operations, custom actions, and OData logic. This agent specializes in Node.js, TypeScript, and Java service development for CAP. Examples: "Implement a custom CREATE handler for Orders entity" "Add a bound action to mark order as completed" "How do I…
go-expert
Go programming language strategist. Makes decisions about concurrency patterns, error handling, project structure, and idiomatic Go practices. Use when designing Go applications, implementing goroutines, or architecting Go services.
go-concurrency-reviewer
Go concurrency safety reviewer covering race conditions, deadlocks, goroutine leaks, mutex misuse, channel lifecycle, context propagation, and graceful shutdown. Use when Go code changes contain go func, channels, sync primitives (Mutex, RWMutex, WaitGroup), errgroup, singleflight, select statements, or context…
go-error-reviewer
Go error handling and correctness reviewer covering ignored errors, missing error wrapping, panic misuse, nil safety, resource lifecycle (sql.Rows, resp.Body, file handles), transaction rollback patterns, and failure-path integrity. Use when Go code changes contain error returns, panic calls, sql.Rows, tx.Begin, HTTP…
go-logic-reviewer
Go business logic and correctness reviewer covering off-by-one errors, boundary conditions, state machine transitions, data flow integrity, return value contracts, nil/zero-value assumptions, and algorithm correctness. Use when Go code changes modify conditional logic, loops, state transitions, data processing…