Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/woliveiras/geremmyasnpx agentmods add skills/woliveiras/geremmyas/go-ci-setupWrote 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/woliveiras/geremmyas/go-ci-setup)<a href="https://agentmods.dev/skills/woliveiras/geremmyas/go-ci-setup"><img src="https://agentmods.dev/badge/skills/woliveiras/geremmyas/go-ci-setup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/woliveiras/geremmyas/go-ci-setup"><img src="https://agentmods.dev/badge/skills/woliveiras/geremmyas/go-ci-setup.svg" alt="Reviewed on agentmods" width="80" 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.00057 | $0.01029 |
| Opus 5 | $0.00028 | $0.00515 |
| Sonnet 5 | $0.00011 | $0.00206 |
| Haiku 4.5 | $0.00006 | $0.00103 |
Grade A, and why
go-ci-setup 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 12d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go CI Setup
Multi-step workflow to create a production-grade Go CI pipeline.
When to Use
- New Go project needs CI from scratch
- Existing project has incomplete or fragile CI
- Adding security scanning, vulnerability checks, or container builds
Pipeline Layers (in order)
Each layer gates the next. If a layer fails, the pipeline stops.
- Format —
gofmt -l .(orgofumpt -l .) must produce no output - Vet —
go vet ./...(built-in, zero-config, no false positives) - Static Analysis —
staticcheck ./...(recommended) orgolangci-lint run - Test —
go test -race -coverprofile=coverage.out ./... - Vulnerability Scan —
govulncheck ./...(reachable vulns only) - Build —
go build -trimpath -ldflags="-s -w" ./cmd/... - Container (optional) — Multi-stage Docker with distroless/static base
Steps
1. Choose CI Platform
Decide between GitHub Actions, GitLab CI, Cloud Build, or other. Default to GitHub Actions for GitHub-hosted repositories.
2. Create Workflow File
For GitHub Actions: .github/workflows/ci.yml
Minimum structure:
name: CI
on:
push:
branches: [main]
pull_request:
branches: [main]
jobs:
ci:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-go@v5
with:
go-version-file: go.mod
- run: gofmt -l . | tee /dev/stderr | (! read)
- run: go vet ./...
- run: go install honnef.co/go/tools/cmd/staticcheck@latest && staticcheck ./...
- run: go test -race -coverprofile=coverage.out ./...
- run: go install golang.org/x/vuln/cmd/govulncheck@latest && govulncheck ./...
- run: go build -trimpath ./cmd/...
3. Add Caching
Use actions/setup-go@v5 which caches ~/go/pkg/mod automatically via
go-version-file. No separate cache step needed.
4. Add Container Build (if applicable)
Multi-stage Dockerfile:
FROM golang:1.24-alpine AS builder
WORKDIR /src
COPY go.mod go.sum ./
RUN go mod download
COPY . .
RUN CGO_ENABLED=0 go build -trimpath -ldflags="-s -w" -o /app ./cmd/server
FROM gcr.io/distroless/static-debian12:nonroot
COPY --from=builder /app /app
ENTRYPOINT ["/app"]
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.
- 12d ago First seen · 118 lines · 57 tokens per session scan A e4171a9093af
go-ci-setup is a skill published in the GitHub repository woliveiras/geremmyas (10 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 1,029 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-31.
Other skills, from other repositories
golang-continuous-integration
GitHub Actions CI/CD pipeline configuration for Golang projects — workflow files for test, lint, SAST, coverage and vulnerability-scan jobs, Dependabot and Renovate config files, GoReleaser release pipelines, Docker build/push, repository security settings, and AI-driven PR review. Use when setting up or improving Go…
go-ci-workflow
Use when creating or refactoring GitHub Actions CI workflows for Go repositories. Covers repository-shape detection, Make-driven delegation with formal fallbacks, Go setup, caching, tool pinning, permissions, reusable workflows, and quality gate design.
go-ci
Continuous integration for Go projects: GitHub Actions pipelines, caching, golangci-lint setup, test/coverage gates, vulnerability scanning, build matrices, and Makefile targets. Use when: "set up CI", "GitHub Actions for Go", "add lint to the pipeline", "CI is slow", "coverage gate", "build matrix", "write a…
go-deploy
Build and deploy Go applications — version detection, static binaries, CGO, workspaces, and Dockerfile patterns. Use when deploying a Go project, or when go.mod is detected.
scaffold-go
Scaffold a complete Go project with CI/CD, release pipeline, Makefile, sr.yaml, .envrc, and standard files. Uses go toolchain and make as the native build system. Loads on top of scaffold-project (run that first for cross-language standard files). Use when creating a new Go CLI, service, or module, or when the user…
scaffold-go-cli
Scaffold a complete Go CLI project with Cobra, GoReleaser, GitHub Actions CI/CD, Homebrew tap publishing, and Makefile. Use when the user says "scaffold a Go CLI", "new Go CLI project", "create a Go CLI", "start a Go CLI", "bootstrap a Go CLI", or starts a Go command-line tool from scratch. Optionally adds Viper for…