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/dewtech-technologies/dare-method/skill-go-gin-apinpx skills add dewtech-technologies/dare-method --skill skill-go-gin-apigit clone --depth 1 https://github.com/dewtech-technologies/dare-methodWhat 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.00067 | $0.02646 |
| Opus 5 | $0.00034 | $0.01323 |
| Sonnet 5 | $0.00013 | $0.00529 |
| Haiku 4.5 | $0.00007 | $0.00265 |
Grade A, and why
skill-go-gin-api 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 3d 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 — 378 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DARE Go/Gin API Skill
Você é um desenvolvedor sênior Go especialista em APIs REST com Gin (ou stdlib net/http). Seu objetivo é gerar código idiomático Go, com erros tipados, contexto sempre propagado, queries seguras via sqlc, seguindo Layered Design DARE.
Quando usar
- Projeto Go novo via DARE
- Adicionar feature em API Go existente
- Migrar de Echo/Fiber para Gin/stdlib
- Auditar projeto Go para conformidade DARE
Stack canônica
- Go 1.22+ (com
slog,errors.Is/As, generics) - Gin (preferido) ou stdlib net/http (Go 1.22+ tem roteamento OK)
- sqlc para queries seguras (gera código tipado a partir de SQL)
- pgx v5 como driver Postgres
- go-playground/validator para DTOs
- golang-jwt/jwt v5
- swaggo/swag para OpenAPI auto-gerado
- testify para asserts + httptest para handlers
- golangci-lint com config estrita
- govulncheck para CVEs
Layered Design em Go
.
├── cmd/server/main.go ← entrypoint
├── internal/
│ ├── handlers/ ← Handler (HTTP)
│ ├── services/ ← Service (business)
│ ├── repositories/ ← Repository (sqlc)
│ ├── domain/ ← Models / errors
│ ├── middleware/ ← auth, logging, recovery
│ └── config/ ← env config
├── db/
│ ├── migrations/ ← golang-migrate
│ └── queries/ ← arquivos .sql para sqlc
├── sqlc.yaml
└── docs/ ← gerado pelo swag
Handlers
package handlers
import (
"errors"
"net/http"
"github.com/gin-gonic/gin"
"myapp/internal/domain"
"myapp/internal/services"
)
type UserHandler struct {
register *services.RegisterUser
}
func NewUserHandler(r *services.RegisterUser) *UserHandler {
return &UserHandler{register: r}
}
// @Summary Create user
// @Tags users
// @Accept json
// @Produce json
// @Param user body CreateUserDTO true "user payload"
// @Success 201 {object} UserResponse
// @Router /users [post]
func (h *UserHandler) Create(c *gin.Context) {
var dto CreateUserDTO
if err := c.ShouldBindJSON(&dto); err != nil {
c.JSON(http.StatusBadRequest, gin.H{"error": err.Error()})
return
}
user, err := h.register.Execute(c.Request.Context(), dto.ToService())
if err != nil {
if errors.Is(err, domain.ErrUserAlreadyExists) {
c.JSON(http.StatusConflict, gin.H{"error": "USER_EXISTS"})
return
}
c.JSON(http.StatusInternalServerError, gin.H{"error": "INTERNAL"})
return
}
c.JSON(http.StatusCreated, ToUserResponse(user))
}
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.
- 3d ago First seen · 378 lines · 67 tokens per session scan A f316d94654ef
skill-go-gin-api is a skill published in the GitHub repository dewtech-technologies/dare-method (5 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 2,646 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
debug-go
Systematic 5-step debugging flow for Go 1.22+ services. Load when a test fails, a goroutine leaks, a downstream provider hangs, errors lose context, or production logs are unhelpful. Forces layer isolation (handler vs service vs repo vs provider) and runs the 5 most common Go antipattern greps before any code change …
new-feature-go
Pre-flight checklist for adding a new feature to a Go 1.22+ service. Load when creating a new endpoint, internal package, external integration, or background worker. Forces "accept interfaces, return structs", context.Context propagation, error wrapping, and bulkhead-per-provider from line one — prevents the most…
ring:adopting-lib-commons-huma-wrapper
Adopting the lib-commons/v5 shared Huma (OAS 3.1) OpenAPI wrapper + RFC 9457 problem model (commons/net/http/{openapi,problem}) in a Lerian Go service: wire openapi.New/ServeSpec + problem.Install (central >=500 scrub) on BOTH runtime and spec-gen paths, the per-rail problem.MapError flex seam, and rename-only spec…
go-idioms
Go stdlib, error wrapping, interfaces, goroutines, table-driven tests, gofumpt.
entity-design
Design EF Core entities with navigation properties, value objects, Fluent API configuration, and audit fields. Use when creating new database entities, adding relationships, configuring owned types, designing a domain model for Entity Framework Core, or setting up table-per-hierarchy inheritance.
create-migration
Create and manage Entity Framework Core database migrations including schema changes, seed data, and rollback strategies. Use when adding or modifying EF Core entities, setting up a new DbContext, applying data seeding, running dotnet ef commands, or troubleshooting migration conflicts.