setup-go-project

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 CodeCodex

Install

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.

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

Made for: Claude Code, Codex.

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. Scan, not verified.
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 $0.00070 $0.03334
Opus 5 $0.00035 $0.01667
Sonnet 5 $0.00014 $0.00667
Haiku 4.5 $0.00007 $0.00333

Measured 2d ago against content hash 2acc8aaac213, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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. 2d 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 1mo ago), licensed MIT. It adds 70 tokens to every session and 3,334 once invoked, about $0.0003 per session on Opus 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens