agentleFS
Sign inStart free
jkeddarijkeddari/go-skills/skills/golang-security/SKILL.md

golang-security

Skill1 starsChanged 4 months agoMITView on GitHub

Golang security engineering for threat modeling, input validation, injection prevention, authentication and authorization boundaries, cryptography, secrets, filesystem and network safety, cookies, sensitive logging, dependency exposure, and security review. Use when implementing or auditing security-sensitive Go code.

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Thinking mode: Use ultrathink for threat modeling, authorization analysis, cryptographic review, and exploitability assessment.

    line 21
  2. Distinctive:

    Add a regression test or verification command where practical.

    line 32
  3. Distinctive:

    Read only the category relevant to the data flow under review:

    line 36

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Persona: You are a senior Go security engineer. Trace attacker-controlled data to security-sensitive effects and report evidence, reachability, and impact.

Thinking mode: Use ultrathink for threat modeling, authorization analysis, cryptographic review, and exploitability assessment.

Go Security

Workflow

  1. Identify assets, trust boundaries, attacker-controlled inputs, privileged effects, and deployment assumptions.
  2. Trace data flows through parsing, validation, storage, commands, templates, files, network calls, and logs.
  3. Confirm reachability and existing controls before reporting a vulnerability.
  4. Rank findings by impact and likelihood; separate confirmed issues from hardening opportunities.
  5. Recommend the smallest fix that restores a clear invariant.
  6. Add a regression test or verification command where practical.

Conditional references

Read only the category relevant to the data flow under review:

  • Threat modeling: threat-modeling.md
  • Authentication, authorization, and service boundaries: architecture.md
  • Injection: injection.md
  • Cryptography: cryptography.md
  • Filesystem: filesystem.md
  • Network and cookies: network.md and cookies.md
  • Secrets and sensitive logging: secrets.md and logging.md
  • Memory safety: memory-safety.md
  • Third-party and supply-chain review: third-party.md
  • Audit checklist: checklist.md

→ See golang-dependencies for module changes, golang-code-quality for non-adversarial correctness, and golang-project for CI gates.

Download now (ZIP)

  • Other versions14 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 14

    1. samber/cc-skills-golang★ 3.6ksame name
    2. unxed/f4★ 247same name
    3. klawisha012/agentsync★ 18same name
    4. alexastrum/skl★ 11same name
    5. tstapler/dotfiles★ 8same name
    6. alexderz/agentic-toolbox★ 5same name
    7. poizoncoded/skills★ 2same name
    8. TeddyAlbina/skills★ 2same name
    9. rockcookies/skills★ 1same name
    10. VerifiedOrganic/onboard★ 1same name

    4 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use golang-swagger, golang-google-wire and 7 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • alexastrumSkill

      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, swaggerignore). Apply when adding or maintaining Swagger/OpenAPI docs in a Go project, or when the codebase imports github.com/swaggo/swag, github.com/swaggo/gin-swagger, github.com/swaggo/echo-swagger, github.com/swaggo/http-swagger, or github.com/swaggo/files.

      Also in 7 projects that use this

    • alexastrumSkill

      golang-google-wire

      Compile-time dependency injection in Golang using google/wire — wire.NewSet, wire.Build, wire.Bind (interface→concrete), wire.Struct, wire.Value, wire.InterfaceValue, wire.FieldsOf, cleanup functions, //go:build wireinject injector files, and generated wire_gen.go. Apply when using or adopting google/wire, when the codebase imports `github.com/google/wire`, or when wiring an application graph at compile time via `wire.Build`. For runtime DI with reflection, see `samber/cc-skills-golang@golang-uber-dig` skill.

      Also in 6 projects that use this

    • rockcookiesSkill

      golang-pkg-go-dev

      Golang package and module documentation and exploration via `godig`, a pkg.go.dev API client (CLI + MCP server) — package docs, API references, symbols, code examples, available versions, importers (who imports a package), licenses, and known vulnerabilities. Read-only, no auth. Use for looking up any Go/Golang library's documentation, API signatures, usage examples, which versions exist, whether a dependency has CVEs, or who imports a package — prefer this over Context7 for any Go package or module. Triggers on: how to use a Go library, Go API docs, import usage, code examples, pkg.go.dev. Not for upgrading dependencies (→ See `golang-dependency-management` skill) or choosing a library (→ See `golang-popular-libraries` skill). Not for local symbols, or for navigating an already-used dependency's resolved source, call sites, or generic instantiations — → See `golang-gopls` skill for those.

      Also in 4 projects that use this

    • +6 more from alexastrum
  • In this repository14 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free