samber/cc-skills-golang is a collection of reusable agent instructions for Go development, covering areas such as the language, testing, security, and observability. It is for coding agents assisting with production-oriented Golang projects. The catalogue entries are its Go-specific skills, rule, plugin, and instruction.
Borrowing it
Nothing to install: this file belongs to samber/cc-skills-golang. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/samber/cc-skills-golang/main/CLAUDE.mdgit clone --depth 1 https://github.com/samber/cc-skills-golangWrote 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.
[](https://agentmods.dev/instructions/samber/cc-skills-golang/claude-md)<a href="https://agentmods.dev/instructions/samber/cc-skills-golang/claude-md"><img src="https://agentmods.dev/badge/instructions/samber/cc-skills-golang/claude-md/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.
<a href="https://agentmods.dev/instructions/samber/cc-skills-golang/claude-md"><img src="https://agentmods.dev/badge/instructions/samber/cc-skills-golang/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.16755 | $0.16755 |
| Opus 5 | $0.08377 | $0.08377 |
| Sonnet 5 | $0.03351 | $0.03351 |
| Haiku 4.5 | $0.01675 | $0.01675 |
Grade A, and why
cc-skills-golang CLAUDE.md 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 903 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Project Overview
This is a Claude Code plugin containing AI agent skills for production-ready Go projects. The repository provides reusable skill definitions that Claude Code can invoke when working on Go codebases.
Facts in CLAUDE.md, procedures in skills. Repository-wide facts, conventions and constraints live here; step-by-step instructions for a technique or library live in a skill body. Duplicating one in the other produces two sources of truth that drift and eventually contradict each other — the same failure Atomic skills and deduplication prevents between skills, one level up.
Project Structure
skills/ # Claude Code skill definitions
<skill-name>/
SKILL.md # Required: metadata + instructions
references/ # Optional: detailed documentation loaded on demand
scripts/ # Optional: executable code
assets/ # Optional: templates, resources, linter configs (.golangci.yml, etc.)
.claude-plugin/ # Plugin metadata and configuration
.cursor-plugin/ # Plugin metadata and configuration (version must match .claude-plugin/plugin.json)
gemini-extension.json # Gemini CLI extension manifest (version must match .claude-plugin/plugin.json)
Agent Skills Specification
All skills MUST conform to the Agent Skills specification. Key requirements are summarized below; the spec is the source of truth when in doubt.
Frontmatter
New skills go in skills/<skill-name>/SKILL.md. Each SKILL.md has YAML frontmatter. Fields per the Agent Skills spec — this project requires all fields marked "Project-required":
| Field | Required | Constraints |
|---|---|---|
name |
Spec-required | 1-64 chars. Lowercase a-z, digits, hyphens. No leading/trailing/consecutive hyphens. Must match parent directory name. |
description |
Spec-required | 1-1024 chars. Describes what the skill does and when to use it — this is the primary triggering mechanism. Be specific and slightly "pushy" to avoid under-triggering. |
license |
Project-required | License name or reference to a bundled license file. Use MIT for this project. |
compatibility |
Project-required | 1-500 chars. Describe actual requirements as capabilities, never tool names — Requires internet access, not Requires WebSearch; the capability holds on every harness, the tool name only on Claude Code. Base: Designed for Claude Code, Codex or similar harness. Extend when needed: add Requires git, Requires internet access, Requires Python 3.14+ and uv, etc. Skills with no special requirements use the base string only. |
metadata |
Project-required | Must include author (string), version (semver a.b.c string, e.g. "1.0.0"), and openclaw (object — see below). Caution: some harnesses (e.g. OpenCode) parse metadata as a flat string→string map and may not preserve the nested openclaw object — don't assume every field survives outside Claude Code. |
user-invocable |
Project-required | Boolean. true for skills invocable as slash commands (e.g. /golang-security), false (default) for contextual skills that auto-trigger. |
allowed-tools |
Project-required | Space-delimited list of pre-approved tools. See "Allowed tools" below. |
paths |
Optional | Glob(s) scoping the skill to specific files/directories (e.g. **/*.go). Recognized by Cursor only — a no-op elsewhere. Add it for skills tied to Go source files to sharpen triggering there; skip it for skills with no natural file-type scope (setup, CI, ecosystem-lookup skills). |
dependencies |
Optional, experimental | List of owner/repo@skill identifiers this skill should always load alongside. Formalizes an existing → See cross-reference as a machine-enforced co-load instead of prose the model might skip. Currently recognized by Antigravity only (third-party-documented, not yet confirmed in Google's official docs) — verify before relying on it, and keep the prose → See reference regardless since it's what every other harness actually reads. |
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.
- 5d ago Changed · +1 lines · +44 tokens per session dbc745d9d109
- 7d ago Changed · +20 lines · +305 tokens per session 2c56f545269e
- 8d ago Changed · +107 lines · +3,267 tokens per session e19b78b12e38
- 11d ago First seen · 776 lines · 13,183 tokens per session scan E acad992968c4
cc-skills-golang CLAUDE.md is an instructions file published in the GitHub repository samber/cc-skills-golang (3,223 stars, last pushed 3d ago), licensed MIT. It adds 16,755 tokens to every session, about $0.0838 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.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.