Security best practices and vulnerability prevention for Golang. Covers injection (SQL, command, XSS), cryptography, filesystem safety, network security, cookies, secrets management, memory safety, and logging. Apply when writing, reviewing, or auditing Go code for security, or when working on any risky code involving crypto, I/O, secrets management, user input handling, or authentication. Includes configuration of security tools.
87
85%
Does it follow best practices?
Impact
95%
1.35xAverage score across 3 eval scenarios
Passed
No known issues
Safe dynamic SQL construction
Parameterized name filter
100%
100%
Parameterized age filter
100%
100%
IN clause numbered placeholders
100%
100%
Role values passed as args
100%
100%
ORDER BY uses allowlist
100%
100%
No user column in SQL string
100%
100%
Safe default sort column
100%
100%
sqlx or pgx library used
0%
0%
Empty roles list handled
100%
100%
Sort order direction validated
100%
100%
DREAD scoring security report
DREAD factors per finding
0%
100%
DREAD score formula
0%
100%
Severity classification
60%
100%
Hardcoded password identified
100%
100%
Hardcoded password severity
100%
100%
SQL finding not dismissed
100%
100%
SQL severity adjusted downward
33%
100%
PII in logs identified
100%
100%
Missing server timeouts identified
0%
100%
Inline comment recommended
0%
0%
HTTP security middleware setup
Content-Security-Policy header
100%
100%
X-Frame-Options header
100%
100%
X-Content-Type-Options header
100%
100%
Strict-Transport-Security header
100%
100%
Referrer-Policy header
100%
100%
Permissions-Policy header
0%
100%
ReadTimeout configured
0%
100%
WriteTimeout configured
0%
100%
IdleTimeout configured
0%
100%
Per-client rate limiter
100%
100%
Client map mutex protection
100%
100%
golang.org/x/time/rate used
100%
100%
e9761db
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.