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 skills add kieutrongthien/skills-fullstack --skill backend-golanggit clone --depth 1 https://github.com/kieutrongthien/skills-fullstackWrote 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/skills/kieutrongthien/skills-fullstack/backend-golang)<a href="https://agentmods.dev/skills/kieutrongthien/skills-fullstack/backend-golang"><img src="https://agentmods.dev/badge/skills/kieutrongthien/skills-fullstack/backend-golang/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/skills/kieutrongthien/skills-fullstack/backend-golang"><img src="https://agentmods.dev/badge/skills/kieutrongthien/skills-fullstack/backend-golang.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.00018 | $0.00676 |
| Opus 5 | $0.00009 | $0.00338 |
| Sonnet 5 | $0.00004 | $0.00135 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
backend-golang 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 11d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend - Go (Gin/Echo)
When to use this skill
- Building or updating Go HTTP APIs using Gin or Echo.
- Adding routes/handlers/middleware, validation, logging, or persistence.
- Improving performance, observability, security, or testing for Go services.
Quick start
- Install deps:
go mod tidy(orgo mod download). - Env: copy
.env.example->.envif present; load viagodotenv/config; set DB URLs, secrets, and service endpoints. - Run:
go run ./...or service-specificmake devif provided. - Test:
go test ./...; lint/format:golangci-lint runandgofmt -w/go fmt ./.... - Build:
go build ./cmd/...or project entry.
Project structure basics
cmd/<service>/main.go: entrypoint; wire router, middleware, config, logger, DI.internal/orpkg/: handlers, services/usecases, repositories, domain models, DTOs.configs/: config files; prefer typed config structs with validation.migrations/: SQL/DDL migrations if applicable.
Coding principles
- Keep handlers thin: parse/validate input, call services/usecases, map errors to HTTP responses.
- Services hold business logic; repositories isolate data access; prefer interfaces for tests.
- Validate inputs; return typed errors and map to consistent JSON error shapes.
- Use context-aware logging with request IDs; never log secrets.
- Prefer
golangci-lintandgo test ./...before merge (see scripts/dev-check.sh).
Patterns and snippets
- See references/snippets.md for Gin/Echo router setup, middleware, handlers, error mapping, and DI patterns.
- Centralize HTTP error responses; include correlation ID; avoid panics in request path.
- Use
context.Contextin all public methods; pass through layers.
Bundled resources
- scripts/dev-check.sh: run pre-commit/PR to enforce gofmt, lint, tests, and optional build.
- references/coding-standards.md: guardrails on layering, validation, errors, logging, and testing.
- references/best-practices.md: deeper guidance for Gin/Echo routing, middleware, observability, performance, and security.
- references/snippets.md: ready-to-copy snippets for Gin and Echo (routing, middleware, handlers, errors).
- assets/pr-template.md: PR checklist with testing evidence and API notes.
- assets/migration-checklist.md: use when adding DB schema changes.
What ships with it
6 files 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.
- 11d ago First seen · 52 lines · 18 tokens per session scan A eca253060255
backend-golang is a skill published in the GitHub repository kieutrongthien/skills-fullstack (2 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 676 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-31.
Other skills, from other repositories
golang-graphql
Implements GraphQL APIs in Golang using gqlgen or graphql-go. Apply when building GraphQL servers, designing schemas, writing resolvers, handling subscriptions, or integrating GraphQL with existing Go HTTP services. Also apply when the codebase imports github.com/99designs/gqlgen or github.com/graph-gophers/graphql-go.
golang-pro
Implements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with generics, interfaces, and robust error handling. Use when building Go applications requiring concurrent programming…
golang-grpc
Provides gRPC usage guidelines, protobuf organization, and production-ready patterns for Golang microservices. Use when implementing, reviewing, or debugging gRPC servers/clients, writing proto files, setting up interceptors, handling gRPC errors with status codes, configuring TLS/mTLS, testing with bufconn, or…
golang-swagger
Golang OpenAPI/Swagger documentation with swaggo/swag — annotation comments (@Summary, @Param, @Success, @Router, @Security), swag init code generation, framework integrations (gin, echo, fiber, chi, net/http), security definitions (Bearer/JWT, OAuth2, API key), and struct tags (swaggertype, enums, example…
layered-architecture-types
Enforce primitive-at-edges / strong-types-in-Business layering and the toBus/fromBusResponse/toDB converter pattern. Use when writing, editing, or auditing Go files under app/, business/domain/, or .../stores/db.
printing-press
Set up a new integration, connector, or CLI binding for any API. Wrap or generate a ship-ready Go CLI from an OpenAPI, HAR, or Postman spec via the lean research -> generate -> build -> shipcheck loop. Use when the user says build a CLI, wrap this API, set up a new integration, add a connector, integrate with a…