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/fmind/dot/goreleasernpx skills add fmind/dot --skill goreleasergit clone --depth 1 https://github.com/fmind/dotWrote 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/fmind/dot/goreleaser)<a href="https://agentmods.dev/skills/fmind/dot/goreleaser"><img src="https://agentmods.dev/badge/skills/fmind/dot/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 | $0.00046 | $0.01090 |
| Opus 5 | $0.00023 | $0.00545 |
| Sonnet 5 | $0.00009 | $0.00218 |
| Haiku 4.5 | $0.00005 | $0.00109 |
Grade A, and why
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 yesterday.
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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GoReleaser
Build, archive, checksum, sign, and publish Go binaries from one .goreleaser.yaml when a v* tag lands. The version, changelog, and tag come from release (git-cliff); images come from ko per containerize; signatures follow cosign.
Workflow
- Config:
goreleaser initwrites a starter; trim it to the minimum and keep GoReleaser out of changelog duty.version: 2 builds: - main: ./cmd/<slug> env: [CGO_ENABLED=0] goos: [linux, darwin] goarch: [amd64, arm64] ldflags: [-s -w -X main.version={{.Version}}] archives: - formats: [tar.gz] checksum: name_template: checksums.txt changelog: disable: true # git-cliff owns CHANGELOG.md and the release notes - Validate:
goreleaser checkafter every edit;goreleaser healthcheckconfirmsgit,cosign, andkoare on the runner. - Local dry run: build every target without a tag and without publishing.
goreleaser release --snapshot --clean goreleaser build --single-target --snapshot --clean -o dist/<slug> # this machine only - CI: a
release.ymlworkflow onpush: tags: ['v*']withpermissions: contents: write(plusid-token: writewhen signing),actions/checkoutwithfetch-depth: 0,jdx/mise-actionfor the toolchain, then the release with git-cliff notes; this workflow owns the GitHub release, so skip thegh release createstep of the release skill.git-cliff --latest --strip all > "$RUNNER_TEMP/notes.md" goreleaser release --clean --release-notes "$RUNNER_TEMP/notes.md" # GITHUB_TOKEN from secrets.GITHUB_TOKEN - Sign and ship images (optional): add
signs:withcmd: cosign,args: [sign-blob, --output-certificate=${certificate}, --output-signature=${signature}, --yes, "${artifact}"],artifacts: checksum, andkos:(repositories,platforms) for a multi-arch image; verify withcosign verify-blobper cosign. - Homebrew (optional):
homebrew_casks:publishes a cask to a tap repository; it needs a token with write access to that repository, notGITHUB_TOKEN. - Verify:
gh release view <tag>lists the archives,checksums.txt, and signatures; finish with the verification steps of release.
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.
- yesterday First seen · 60 lines · 46 tokens per session scan A 01f6a496a7b1
goreleaser is a skill published in the GitHub repository fmind/dot (4 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 1,090 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
go-stack
Build Go projects, libraries, CLIs, TUIs, web apps, or ADK agents with the standard package layout and pinned tooling.
python-stack
Build typed Python projects with uv, Ruff, ty, pytest, Litestar, and Typer. Use for packages, CLIs, web apps, tests, typing, or API verification.
release
Cut or verify a versioned release — bump semver, generate the changelog with git-cliff, tag and publish on GitHub, or reconcile an already-published tag and assets.
python-script
Write standalone single-file Python scripts using PEP 723 inline metadata and uv. Use when creating a quick CLI script that needs dependencies without a full project.
dot-release
Prepare, tag, and push a versioned fmind/dotfiles release locally to trigger GitHub Actions CD publication.
k8s-local
Create and manage local Kubernetes clusters (k3d or kind) and deploy to them with kubectl, helm, helmfile, and skaffold. Use for local k8s cluster setup, dev loops, and debugging.