Golang security

Skill serpro69/claude-toolbox/cmd/vendor-profiles/testdata/skills/golang-security

Minimal by design, explicitly multi-lang, production-ready and battle-tested collection of configs and plugins for your Claude Code agentic development workflows: mcp, configs, skills, agents and more.

Install

npx -y skills add serpro69/claude-toolbox --skill golang-security

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

What its author says it does

Copied from the file, not written here

A Go security skill for reviewing code

SKILL.md

0.6 KB, 120 tokens by cl100k_base, as published. Nobody here has run it

You are a Go security expert. Review code for vulnerabilities.

Go Security Checklist

Injection Prevention

Always use parameterized queries for SQL. Never pass user input directly to exec.

See injection details for more.

Cryptography

Use crypto/rand, not math/rand. See Go docs.

Also see golang-testing for testing crypto code.

Authentication

Validate JWT tokens properly. See auth notes for details.

Gives 1 of the 12 instructions most security skills give in 120 tokens

Counted across 648 of the 828 authors here whose files we hold, read 2026-08-06

parameterize all database querieshere, and in 67 of 648, across 49 files
hash passwords using bcrypt scrypt or argon2in 48 of 648, across 35 files
apply rate limiting to authentication endpointsin 48 of 648, across 24 files
Configure security headersin 35 of 648, across 18 files
validate all inputsin 32 of 648, across 24 files
validate all external input at the system boundaryin 29 of 648, across 18 files
run containers as a non-root userin 28 of 648, across 15 files
use httponly secure samesite cookies for sessionsin 26 of 648, across 15 files
run dependency audits before every releasein 21 of 648, across 10 files
encode output to prevent cross-site scriptingin 21 of 648, across 10 files
copy dependencies before source codein 20 of 648, across 9 files
store secrets in environment variablesin 20 of 648, across 17 files

Said here and by no other author read

use crypto/rand instead of math/rand

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.