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.
npx agentmods add commands/car12o/claude-workflows/gopher-initgit clone --depth 1 https://github.com/car12o/claude-workflowsWrote 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/commands/car12o/claude-workflows/gopher-init)<a href="https://agentmods.dev/commands/car12o/claude-workflows/gopher-init"><img src="https://agentmods.dev/badge/commands/car12o/claude-workflows/gopher-init.svg" alt="Measured on agentmods" 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 | $0.00023 | $0.01351 |
| Opus 5 | $0.00012 | $0.00675 |
| Sonnet 5 | $0.00005 | $0.00270 |
| Haiku 4.5 | $0.00002 | $0.00135 |
Grade A, and why
gopher-init 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 — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scaffold a new Go 1.24+ project.
Arguments
Parse from $ARGUMENTS:
- module-path (required): Go module path (e.g.,
github.com/org/project) - --layout (optional):
minimal,standard(default), orservice
If no arguments provided, ask the user for the module path.
Layouts
minimal
project/
├── go.mod
├── main.go
├── main_test.go
├── Makefile
└── README.md
standard
project/
├── cmd/
│ └── server/
│ └── main.go
├── internal/
│ ├── domain/
│ ├── service/
│ ├── repository/
│ ├── handler/
│ └── config/
├── pkg/
├── migrations/
├── go.mod
├── Makefile
├── .golangci.yml
├── Dockerfile
└── README.md
service
project/
├── cmd/
│ ├── api/
│ │ └── main.go
│ └── worker/
│ └── main.go
├── internal/
│ ├── domain/
│ ├── service/
│ ├── repository/
│ ├── handler/
│ └── config/
├── pkg/
├── migrations/
├── go.mod
├── Makefile
├── .golangci.yml
├── Dockerfile
└── README.md
Steps
1. Pre-flight Check
Check which files and directories from the chosen layout already exist. Track them — subsequent steps will skip existing files rather than overwriting them.
2. Create Directory Structure
Report: "Creating directory structure..."
Create directories based on the chosen layout. Skip directories that already exist.
3. Initialize Module
Report: "Initializing Go module..."
Skip if go.mod already exists.
go mod init <module-path>
Then edit go.mod to set Go 1.24.
For standard and service layouts, add tool directives:
module <module-path>
go 1.24
tool (
golang.org/x/tools/cmd/goimports
github.com/golangci/golangci-lint/cmd/golangci-lint
golang.org/x/vuln/cmd/govulncheck
)
For minimal:
module <module-path>
go 1.24
4. Create main.go
Skip if the target main.go already exists.
For minimal:
package main
import "fmt"
func main() {
fmt.Println("Hello, World!")
}
For standard and service (cmd/server/main.go or cmd/api/main.go):
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.
- 3d ago First seen · 274 lines · 23 tokens per session scan A 98b969c05702
gopher-init is a command published in the GitHub repository car12o/claude-workflows (2 stars, last pushed 6mo ago), licensed MIT. It adds 23 tokens to every session and 1,351 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-31.
Other commands, from other repositories
trex.kind.add-field
Add a new field to an existing Kind, updating all layers consistently.
go-review
Go code review for idiomatic patterns.
cli-patterns
Reference patterns for implementing CLI commands in internal/cli/.
go-conventions
Scan the current Go repo and write .claude/go-conventions.md — a project-specific convention file that rules/go.md loads on every session instead of re-scanning the codebase from scratch. Use when starting work in a new Go repo, when conventions have drifted, or when --refresh is passed to merge in new patterns.
add-test-fixture-and-go-test-for-langgraph-js-rule
Workflow command scaffold for add-test-fixture-and-go-test-for-langgraph-js-rule in shingan.
go-build
Fix Go build errors, go vet warnings, and linter issues incrementally. Invokes the go-build-resolver agent for minimal, surgical fixes.