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 skills/sgaunet/claude-plugins/go-structurenpx skills add sgaunet/claude-plugins --skill go-structuregit clone --depth 1 https://github.com/sgaunet/claude-pluginsWrote 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/skills/sgaunet/claude-plugins/go-structure)<a href="https://agentmods.dev/skills/sgaunet/claude-plugins/go-structure"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/go-structure.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.00057 | $0.03160 |
| Opus 5 | $0.00028 | $0.01580 |
| Sonnet 5 | $0.00011 | $0.00632 |
| Haiku 4.5 | $0.00006 | $0.00316 |
Grade A, and why
go-structure 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 4d 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 — 373 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Project Structure
Recommend and scaffold idiomatic Go project layouts. Matches structure to project type and size — start simple, grow when needed.
When to Use
- Initializing a new Go project or module
- User asks about project layout or directory organization
- Reviewing an existing project for structural anti-patterns
- Migrating from flat layout to a more structured one
- Setting up a monorepo with multiple services
Prerequisites
- go.mod exists or will be created: The project must be a Go module.
- Project type is known or inferrable: CLI tool, REST API, library, or monorepo.
Core Principle
Simplicity first, complexity when necessary. Do not impose structure upfront. Let it emerge from actual needs. A single main.go is a valid starting point.
Anti-Patterns to Flag
| Anti-Pattern | Problem | Fix |
|---|---|---|
Generic package names (utils, helpers, common, base) |
Become dumping grounds, convey no intent | Rename to specific purpose: validator, auth, cache |
Over-nesting (internal/services/user/handlers/http/v1/) |
Cognitive load, cumbersome imports | Flatten to internal/user/handler.go |
Circular dependencies (A imports B, B imports A) |
Compilation error, poor separation | Extract shared types into a separate package or use interfaces |
| Business logic in HTTP handlers | Couples domain to transport, hard to test | Move to service layer, handlers only do HTTP concerns |
The main.go monster (all logic in one file) |
Untestable, circular deps, impossible to maintain | Extract into packages; main.go only wires deps and starts |
| Shared database across microservices | Distributed monolith, schema changes break all services | Each service owns its data; communicate via APIs |
Using pkg/ for non-library code |
Misleading signal, unnecessary indirection | Move to internal/ or project root |
Premature cmd/ for single-binary projects |
Unnecessary nesting | Keep main.go at root until multiple binaries are needed |
| Hardcoded DB credentials / config values | Security risk, not deployable across environments | Use env vars or config system; never commit secrets |
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.
- 4d ago First seen · 373 lines · 57 tokens per session scan A 7ceff4e181ed
go-structure is a skill published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 2d ago), licensed MIT. It adds 57 tokens to every session and 3,160 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-30.
Other skills, from other repositories
ab-test-analysis
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
brainstorm-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
outcome-roadmap
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
pre-mortem
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go…
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.