go-guidelines

A set of coding guidance for Go, a programming language used for fast and concurrent software. It covers code structure, modern language features, testing, errors, performance, and concurrency.

In plain words
What is it for?
Use it when writing, reviewing, testing, or improving Go code, especially code that needs efficient execution or uses concurrent operations.
Why use it?
It helps an agent produce Go code that follows established practices and avoids common mistakes in areas such as error handling and concurrent work.

Plugin for Claude Code

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.

Claude Code
/plugin marketplace add mhmtszr/go-guidelines
agentmods
npx agentmods add plugins/mhmtszr/go-guidelines/go-guidelines
Clone the repo
git clone --depth 1 https://github.com/mhmtszr/go-guidelines

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured The manifest loads nothing itself; its 1 skill cost 34 tokens a session between them.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

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

.claude-plugin/plugin.json · 22 lines

What it actually says

{
  "name": "go-guidelines",
  "description": "Enhances code agents with Go best practices covering performance, modern syntax, generics, patterns, testing, error handling, and concurrency.",
  "version": "1.2.0",
  "author": {
    "name": "Mehmet Sezer",
    "email": "[email protected]"
  },
  "homepage": "https://github.com/mhmtszr/go-guidelines",
  "repository": "https://github.com/mhmtszr/go-guidelines",
  "license": "MIT",
  "keywords": [
    "go",
    "golang",
    "go-best-practices",
    "guidelines",
    "performance",
    "testing",
    "error-handling"
  ]
}
Contents

What it installs

The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 34 tokens a session between them. Each is measured on its own page, and each can be installed alone.

Files

What ships with it

1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 3d ago First seen · 22 lines scan A 45f18d6957fe

Subscribe to this mod's changes

go-guidelines is a plugin published in the GitHub repository mhmtszr/go-guidelines (103 stars, last pushed 5d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories

cli-printing-press

Generate production Go CLIs from API descriptions or OpenAPI specs.

mvanhorn/cli-printing-press · not measured

cobra-viper

Definitive guide to building CLI applications with Cobra and Viper — command-first architecture, configuration management, environment variable binding, and in-memory CLI testing. Written by spf13, the original creator of both libraries.

PascaleBeier/hitkeep · not measured

go-spec-reviewer

Review Go design documents before implementation begins — catches over-engineering, missing error paths, interface misuse, and Cobra/Viper convention violations while a plan is still cheap to change.

PascaleBeier/hitkeep · not measured

go-ultimate

Opinionated Go development skill — architecture, conventions, production readiness, repo/CI hygiene, review, and MCP/agent patterns.

Djarvur/go-ultimate · not measured

go-specialist

Master Go 1.25+ development with modern patterns, advanced concurrency, performance optimization, and production-ready microservices. Skills: go-blackbox (black box test enforcement), go-bulma (Bulma CSS scaffolding), go-structure (project layout), go-tool (Go 1.24+ tool dependencies). MCP: context7.

sgaunet/claude-plugins · not measured

golang-skills

20 modular skills for idiomatic Go — each under 225 lines, backed by 48 reference files, 8 automation scripts (all with --json, --limit, --force), and 4 asset templates. Covers error handling, naming, testing, concurrency, interfaces, generics, documentation, logging, performance, and more. Activates automatically…

cxuu/golang-skills · not measured