Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add sgaunet/claude-plugins/plugin install go-specialistWrote 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/sgaunet/claude-plugins/gen-goreleaser)<a href="https://agentmods.dev/commands/sgaunet/claude-plugins/gen-goreleaser"><img src="https://agentmods.dev/badge/commands/sgaunet/claude-plugins/gen-goreleaser.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.1 | $0.00021 | $0.05155 |
| Opus 5 | $0.00010 | $0.02577 |
| Sonnet 5 | $0.00004 | $0.01031 |
| Haiku 4.5 | $0.00002 | $0.00515 |
Grade A, and why
gen-goreleaser 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 6d 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 — 603 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate GoReleaser Configuration Command
Instantly create complete GoReleaser setup for Go projects with multi-architecture Docker builds, automated releases, and package distribution. This command converts the multi-step goreleaser skill into a one-command solution.
Why This Command Exists
Problem: Setting up GoReleaser requires:
- Creating complex YAML configuration (~300 lines)
- Designing multi-stage Dockerfiles for cross-platform builds
- Configuring non-root container users
- Understanding ldflags, build matrix, Docker buildx
- Testing across multiple architectures A 60-90 minute process requiring deep GoReleaser knowledge.
Solution: One-command generation that:
- Creates production-ready
.goreleaser.yml(316 lines) - Includes optimized
Dockerfilefor multi-arch builds - Sets up non-root container user configuration
- Auto-detects project structure and binary names
- Supports standard (full) and minimal modes
- Preserves all customization comments
Content Generation Rules
CRITICAL: When generating any content (configuration files, Dockerfiles, commit messages, or any other output):
- NEVER add Claude Code attribution or co-authorship
- NEVER include phrases like "Generated by Claude", "Created with Claude Code", or similar
- NEVER add "Co-Authored-By: Claude" in commit messages or documentation
- All generated content should appear as if written by a human developer
- Focus on technical accuracy and providing working templates
Process (7 Phases)
Phase 1: Prerequisites Validation
Critical checks before proceeding:
-
Validate Git repository:
git rev-parse --git-dir- If fails: Exit with error "Not a git repository. Run 'git init' first."
-
Validate Go project:
test -f go.mod- If fails: Exit with error "go.mod not found. This command is for Go projects only."
-
Check existing GoReleaser files:
test -f .goreleaser.yml || test -f .goreleaser.yaml test -f Dockerfile test -d resources/etc- Store results:
existingConfig = true/false(for .goreleaser.yml/yaml)existingDockerfile = true/falseexistingResources = true/falseexistingFile = <filename>if config exists
- Store results:
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.
- 6d ago First seen · 603 lines · 21 tokens per session scan A a0ec54f4ef39
gen-goreleaser is a command published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 4d ago), licensed MIT. It adds 21 tokens to every session and 5,155 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.
Other commands, from other repositories
sprint
Sprint lifecycle — plan a sprint, run a retrospective, or generate release notes.
version-bump
Bump versions across the monorepo during release process.
release
Generate changelog, bump version, and create git tag.
cancel-ship
Cancel active ship pipeline.
bump-version
Bump semver version for single or multiple plugins based on change analysis.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.