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 skills/mtnyilmaz/agents/go-developernpx skills add mtnyilmaz/agents --skill go-developergit clone --depth 1 https://github.com/mtnyilmaz/agentsWhat 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.00053 | $0.01494 |
| Opus 5 | $0.00026 | $0.00747 |
| Sonnet 5 | $0.00011 | $0.00299 |
| Haiku 4.5 | $0.00005 | $0.00149 |
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 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Developer
Expert in idiomatic Go for production backend services.
Reference Rules
Load these rules for the relevant context:
.agents/layers/language/go/go-patterns.md— idiomatic Go, error handling, concurrency, testing.agents/layers/concern/backend/api-design.md— REST API design principles.agents/layers/universal/security-baseline.md— security requirements.agents/layers/universal/error-handling.md— error handling principles
Core Go Architecture
/cmd
/api
main.go ← entry point: setup, wire dependencies, start server
/internal ← private application code (cannot be imported externally)
/user ← one package per domain
handler.go ← HTTP handlers (parse request → call service → write response)
service.go ← business logic
repository.go ← database access
model.go ← domain types, DTOs, input/output structs
service_test.go ← tests next to source
handler_test.go
/middleware
auth.go
logging.go
rate_limit.go
/config
config.go ← load and validate env vars (envconfig or viper)
/pkg ← reusable code safe for external import
/apperr ← shared error types
/httputil ← shared HTTP helpers
/dbutil ← shared DB helpers
/migrations ← SQL migration files (golang-migrate or goose)
Dependency Injection — Constructor Injection
// ✅ Explicit dependency injection — testable, no globals
type UserService struct {
repo UserRepository
emailSender EmailSender
logger *slog.Logger
}
func NewUserService(repo UserRepository, email EmailSender, logger *slog.Logger) *UserService {
return &UserService{repo: repo, emailSender: email, logger: logger}
}
Never use init() or global variables for dependencies — they make testing impossible.
Repository Pattern
// Define interface in the domain package
type UserRepository interface {
GetByID(ctx context.Context, id string) (*User, error)
GetByEmail(ctx context.Context, email string) (*User, error)
Create(ctx context.Context, input CreateUserInput) (*User, error)
Update(ctx context.Context, id string, input UpdateUserInput) (*User, error)
SoftDelete(ctx context.Context, id string) error
List(ctx context.Context, filter UserFilter) ([]User, int, error)
}
// Implement with concrete DB driver
type postgresUserRepo struct {
db *pgxpool.Pool
}
func (r *postgresUserRepo) GetByID(ctx context.Context, id string) (*User, error) {
var user User
err := r.db.QueryRow(ctx,
`SELECT id, email, name, role, created_at
FROM users WHERE id = $1 AND deleted_at IS NULL`,
id,
).Scan(&user.ID, &user.Email, &user.Name, &user.Role, &user.CreatedAt)
if errors.Is(err, pgx.ErrNoRows) {
return nil, ErrNotFound
}
if err != nil {
return nil, fmt.Errorf("UserRepo.GetByID: %w", err)
}
return &user, nil
}
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 202 lines · 53 tokens per session scan A 08589d842b78
go-developer is a skill published in the GitHub repository mtnyilmaz/agents (6 stars, last pushed 3mo ago), licensed MIT. It adds 53 tokens to every session and 1,494 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…