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/dewtech-technologies/dare-methodWrote 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/commands/dewtech-technologies/dare-method/skill-go-gin-api)<a href="https://agentmods.dev/commands/dewtech-technologies/dare-method/skill-go-gin-api"><img src="https://agentmods.dev/badge/commands/dewtech-technologies/dare-method/skill-go-gin-api/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/commands/dewtech-technologies/dare-method/skill-go-gin-api"><img src="https://agentmods.dev/badge/commands/dewtech-technologies/dare-method/skill-go-gin-api.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.00000 | $0.01672 |
| Opus 5.5 | $0.00000 | $0.00669 |
| Sonnet 5.5 | $0.00000 | $0.00334 |
| Haiku 4.5 | $0.00000 | $0.00167 |
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 1mo 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/skill-go-gin-api
Padrões DARE para APIs REST em Go + Gin (ou stdlib net/http) + sqlc + PostgreSQL. Handlers, services, repositories, middleware, validador, JWT, rate limit, swag OpenAPI.
Como usar
/skill-go-gin-api # audita projeto Go
/skill-go-gin-api scaffold users # gera handler + service + repo + sqlc query
/skill-go-gin-api migrate-validation # extrai json.Unmarshal manual para binding tags
Stack canônica
- Go 1.22+ (slog, errors.Is/As, generics)
- Gin (preferido) ou stdlib net/http
- sqlc (queries seguras geradas de SQL)
- pgx v5
- go-playground/validator (via Gin binding tags)
- golang-jwt/jwt v5
- swaggo/swag (OpenAPI)
- testify + httptest
- golangci-lint + govulncheck
Estrutura
cmd/server/main.go
internal/
├── handlers/ ← Handler
├── services/ ← Service
├── repositories/ ← Repository (sqlc)
├── domain/ ← Models + erros sentinela
├── middleware/
└── config/
db/
├── migrations/ ← golang-migrate
└── queries/ ← .sql para sqlc
sqlc.yaml
Handler
// @Summary Create user
// @Router /users [post]
func (h *UserHandler) Create(c *gin.Context) {
var dto CreateUserDTO
if err := c.ShouldBindJSON(&dto); err != nil {
c.JSON(400, 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(409, gin.H{"error": "USER_EXISTS"})
return
}
c.JSON(500, gin.H{"error": "INTERNAL"})
return
}
c.JSON(201, ToUserResponse(user))
}
DTO
type CreateUserDTO struct {
Email string `json:"email" binding:"required,email"`
Name string `json:"name" binding:"required,min=1,max=255"`
Password string `json:"password" binding:"required,min=12"`
}
Service
type RegisterUser struct {
repo *repositories.UserRepository
}
func (s *RegisterUser) Execute(ctx context.Context, in RegisterUserInput) (*domain.User, error) {
exists, err := s.repo.ExistsByEmail(ctx, in.Email)
if err != nil { return nil, err }
if exists { return nil, domain.ErrUserAlreadyExists }
return s.repo.Create(ctx, repositories.CreateUserParams{
Email: in.Email,
Name: in.Name,
PasswordHash: hashPassword(in.Password),
})
}
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.
- 1mo ago First seen · 233 lines · 0 tokens per session scan A ba0de0fd3afe
skill-go-gin-api is a command published in the GitHub repository dewtech-technologies/dare-method (5 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,672 tokens. 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-09-03.
Other commands, from other repositories
api-gen
Generate REST API endpoints with routes, validation, error handling, and tests.
ccc-python-review
Review changed Python code for security, type safety, error handling, idioms and framework pitfalls, with static analysis results and a merge verdict. Use after editing .py files, before committing Python changes, or when reviewing a Python pull request.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.