setup-go-project

setup-go-project is a skill for Claude Code from phobologic/claude_code_helpers. It costs 70 tokens per session (3,334 once invoked), scanned A, original, MIT.

A setup workflow for creating a new Go project with a standard layout and development checks. Go is a programming language, and the workflow includes files for building, testing, linting, formatting, continuous integration, and Git hooks.

In plain words
What is it for?
Use it to scaffold a Go command-line project, configure its module and build commands, add GitHub Actions, and set up checks before commits and pushes.
Why use it?
It removes the repetitive setup needed to make a small Go project ready for local development and automated checks.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: model in frontmatter; reads .claude/ paths; positional $N argument.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is go build -ldflags "$(LDFLAGS)" -o $(BINARY) ./cmd/$(BINARY).

Good fit Use it to scaffold a Go command-line project, configure its module and build commands, add GitHub Actions, and set up checks before commits and pushes.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/phobologic/claude_code_helpers
agentmods
npx agentmods add skills/phobologic/claude_code_helpers/setup-go-project

Made for: Claude Code.

Wrote 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.

agentmods badge for setup-go-project

README.md
[![agentmods](https://agentmods.dev/badge/skills/phobologic/claude_code_helpers/setup-go-project/github.svg)](https://agentmods.dev/skills/phobologic/claude_code_helpers/setup-go-project)
Your own site
<a href="https://agentmods.dev/skills/phobologic/claude_code_helpers/setup-go-project"><img src="https://agentmods.dev/badge/skills/phobologic/claude_code_helpers/setup-go-project/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.

agentmods 80×15 button for setup-go-project

Your own site · 80×15
<a href="https://agentmods.dev/skills/phobologic/claude_code_helpers/setup-go-project"><img src="https://agentmods.dev/badge/skills/phobologic/claude_code_helpers/setup-go-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,334 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00070 $0.03334
Opus 5.5 $0.00028 $0.01334
Sonnet 5.5 $0.00014 $0.00667
Haiku 4.5 $0.00007 $0.00333

Measured 1mo ago against content hash 2acc8aaac213, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

setup-go-project 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.

skills/setup-go-project/SKILL.md · 437 lines

How it starts

The opening of the file, as written. The whole thing — 437 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Setup Go Project

Scaffold a new Go project with opinionated defaults: a cmd/<name>/main.go layout, a Makefile with build/test/lint/fmt/clean/cover targets, golangci-lint for linting, GitHub Actions for CI, and a two-layer git-hook setup — fast gate at pre-commit (goimports + go vet) and full gate at pre-push (make lint && make test, mirroring CI).

Phase 1 — Determine project name and module path

  • If $ARGUMENTS is non-empty, use it as the project name
  • Otherwise, infer from basename $PWD
  • Ask the user for the Go module path (e.g. github.com/<user>/<name>). Do not guess — wrong module paths are painful to change later. If go.mod already exists, read the module path from it instead of asking.

Present a brief summary, then ask for confirmation. If .git/ exists, include the hook files in the list; otherwise omit them and note that hooks will be skipped until git is initialized.

For new projects:

Project name:    <name>
Module path:     <module-path>
Binary:          <name> (in cmd/<name>/)
Files to create: go.mod, Makefile, .gitignore, README.md, .golangci.yml,
                 cmd/<name>/main.go, .github/workflows/ci.yml
Git hooks:       .git/hooks/pre-commit, .git/hooks/pre-commit.d/go.sh,
                 .git/hooks/pre-push,   .git/hooks/pre-push.d/go.sh
                 (or: "skipped — git not initialized")

Proceed? [y/N]

For existing projects (re-run), show what will be added/updated:

Project name:    <name> (existing project)

Updates:
  .golangci.yml:           add <missing linters>
  Makefile:                add <missing targets>
  .github/workflows/ci.yml: already up to date
  pre-push.d/go.sh:        add (hook is new)

Proceed? [y/N]

Phase 2 — Preflight checks

Before writing anything:

  1. Check which target files already exist. Read each existing file so you understand what's already configured.
  2. Check if git is initialized (git rev-parse --git-dir 2>/dev/null). If not, note it in the final report — don't run git init yourself.
  3. Check if go and golangci-lint are on PATH. If golangci-lint is missing, note the install command (brew install golangci-lint or go install github.com/golangci/golangci-lint/v2/cmd/golangci-lint@latest) in the final report.

Read the full file on GitHub · 437 lines

Changes

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.

  1. 1mo ago First seen · 437 lines · 70 tokens per session scan A 2acc8aaac213

Subscribe to this mod's changes

setup-go-project is a skill published in the GitHub repository phobologic/claude_code_helpers (5 stars, last pushed 5d ago), licensed MIT. It adds 70 tokens to every session and 3,334 once invoked, about $0.0003 per session on Opus 5.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.

Related

Other skills, from other repositories

golang-continuous-integration

GitHub Actions CI/CD pipeline configuration for Golang projects — workflow files for test, lint, SAST, coverage and vulnerability-scan jobs, Dependabot and Renovate config files, GoReleaser release pipelines, Docker build/push, repository security settings, and AI-driven PR review. Use when setting up or improving Go…

samber/cc-skills-golang · 181 tokens

tree-sitter-language-pack-managing-parsers

Use when the user needs to manage the tree-sitter parser cache — prefetch parsers for offline or CI runs, list what is downloaded, inspect a language, find the cache directory, or clean it. Covers ts-pack download, list, info, cache-dir, clean, and init.

xberg-io/tree-sitter-language-pack · 65 tokens

go-ci

Continuous integration for Go projects: GitHub Actions pipelines, caching, golangci-lint setup, test/coverage gates, vulnerability scanning, SAST (CodeQL, gosec), Dependabot, action pinning, build matrices, Makefile targets. Use when: "set up CI", "GitHub Actions for Go", "add lint to the pipeline", "CI is slow"…

eduardo-sl/go-agent-skills · 142 tokens

go-ci-workflow

Use when creating or refactoring GitHub Actions CI workflows for Go repositories. Covers repository-shape detection, Make-driven delegation with formal fallbacks, Go setup, caching, tool pinning, permissions, reusable workflows, and quality gate design.

johnqtcg/awesome-skills · 53 tokens

go-deploy

Build and deploy Go applications — version detection, static binaries, CGO, workspaces, and Dockerfile patterns. Use when deploying a Go project, or when go.mod is detected.

nixopus/nixopus · 41 tokens

scaffold-go

Scaffold a complete Go project with CI/CD, release pipeline, Makefile, sr.yaml, .envrc, and standard files. Uses go toolchain and make as the native build system. Loads on top of scaffold-project (run that first for cross-language standard files). Use when creating a new Go CLI, service, or module, or when the user…

urmzd/dotfiles · 116 tokens