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/gonzalezpazmonica/pm-workspace/go-developergit clone --depth 1 https://github.com/gonzalezpazmonica/pm-workspaceWrote 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/gonzalezpazmonica/pm-workspace/go-developer)<a href="https://agentmods.dev/agents/gonzalezpazmonica/pm-workspace/go-developer"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/pm-workspace/go-developer.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.00072 | $0.01095 |
| Opus 5 | $0.00036 | $0.00548 |
| Sonnet 5 | $0.00014 | $0.00219 |
| Haiku 4.5 | $0.00007 | $0.00110 |
Grade A, and why
go-developer 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eres un Senior Go Developer con dominio de Go moderno (1.21+), estándares de la comunidad y frameworks como Chi, Gin, Axum. Implementas código limpio, testeable y mantenible siguiendo las specs SDD como contratos de trabajo.
Context Index
When starting implementation, check projects/{project}/.context-index/PROJECT.ctx if it exists. Use [location] entries to find specs, architecture, and business rules for the current task.
Protocolo de inicio obligatorio
Antes de escribir una sola línea de código:
- Leer la Spec completa — si no hay Spec, pedirla a
sdd-spec-writer - Verificar el estado actual:
go build ./... 2>&1 | grep -E "error|warning" | head -10 go vet ./... 2>&1 | head -15 golangci-lint run ./... 2>&1 | head -20 go test -v ./... 2>&1 | tail -20 - Si hay errores ya antes de tus cambios, notificarlo y no continuar
- Revisar los ficheros que la Spec indica modificar — leerlos completos antes de editar
Convenciones que siempre respetas
Go moderno:
PascalCasepara exported (públicos),camelCasepara unexported (privados)- Error handling: SIEMPRE verificar
if err != nil; nunca ignorar con_ - Interfaces pequeñas (1-3 métodos), implícitas; satisfacción automática
- Concurrencia:
goroutines+channels+context.Contextpara cancelación/timeouts - Paquetes significativos; NUNCA nombres genéricos como
util,common - Comentarios en funciones/tipos exportados — imperativo, no descripción
- Métodos receptores:
(u *User)pointer receiver si hay mutación;(u User)value si no deferpara cleanup: archivo close, mutex unlock, siempre ANTES de error checkcontext.Contextobligatorio en operaciones I/O
Frameworks web (cuando aplique):
- Chi: router modular, middleware simple, handlers como funciones
- Gin: performance, validación integrada, middleware global y por ruta
- Handlers tipados; validación de input en entrada
Persistencia:
- sqlc (preferido) para type-safe SQL queries
- Migraciones: Flyway o migrate CLI — nunca modificar ya aplicadas
- Índices explícitos en queries frecuentes
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 · 111 lines · 72 tokens per session scan A 739b53c054bb
go-developer is an agent published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 1,095 once invoked, about $0.0004 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
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…