go-standard

A Go programming style guide based on Go's standard library. It covers project structure, naming, error handling, and tests.

In plain words
What is it for?
Use it when organizing Go services, naming packages and files, wrapping and checking errors, writing table-based tests, and separating integration tests.
Why use it?
It gives backend code a consistent shape, making it easier to understand where code belongs and how errors and tests should work.

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/ggombee/code-forge/go-standard
Any agent
npx skills add ggombee/code-forge --skill go-standard
Clone the repo
git clone --depth 1 https://github.com/ggombee/code-forge

Made for: Claude Code, Codex.

Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 392 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.00017 $0.00392
Opus 5 $0.00009 $0.00196
Sonnet 5 $0.00003 $0.00078
Haiku 4.5 $0.00002 $0.00039

Measured 2d ago against content hash b96051604dd4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

go-standard 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.

modules/frameworks/go-standard/SKILL.md · 45 lines

What it actually says

Go 표준 라이브러리 컨벤션

프로젝트 구조

cmd/
└── server/
    └── main.go      # 진입점
internal/            # 외부 노출 불가 패키지
├── handler/         # HTTP 핸들러
├── service/         # 비즈니스 로직
├── repository/      # 데이터 접근 레이어
└── model/           # 도메인 모델
pkg/                 # 외부 공유 가능 패키지
go.mod
go.sum

네이밍 규칙

  • 패키지명: 소문자 단어 (예: handler, repository)
  • 파일명: snake_case.go
  • exported: PascalCase, unexported: camelCase
  • 인터페이스: 동작 기반 이름 (예: UserStore, Notifier)
  • 에러 변수: Err 접두사 (예: ErrNotFound)

에러 처리

  • fmt.Errorf("...: %w", err) 로 에러 래핑
  • errors.Is / errors.As 로 타입 확인
  • 핸들러에서만 HTTP 상태로 변환, 내부 레이어는 순수 에러 반환
  • sentinel 에러는 패키지 레벨에 var ErrXxx = errors.New(...) 정의

테스트

  • testing 표준 패키지 + testify/assert 조합
  • 인터페이스 기반 mock (mockery 또는 수동 mock)
  • 테이블 기반 테스트(t.Run) 적극 활용
  • 통합 테스트는 _integration_test.go 파일로 분리, -tags integration 빌드 태그 사용
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 · 45 lines · 17 tokens per session scan A b96051604dd4

Subscribe to this mod's changes

go-standard is a skill published in the GitHub repository ggombee/code-forge (13 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 392 once invoked, about $0.0001 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-30.

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

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 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

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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens