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/skills/sgaunet/claude-plugins/gen-gitlab-ci)<a href="https://agentmods.dev/skills/sgaunet/claude-plugins/gen-gitlab-ci"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/gen-gitlab-ci/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/sgaunet/claude-plugins/gen-gitlab-ci"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/gen-gitlab-ci.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.00024 | $0.04794 |
| Opus 5.5 | $0.00010 | $0.01918 |
| Sonnet 5.5 | $0.00005 | $0.00959 |
| Haiku 4.5 | $0.00002 | $0.00479 |
Grade A, and why
gen-gitlab-ci 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 22d 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 — 506 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate GitLab CI Configuration
Instantly create a .gitlab-ci.yml file for Go projects with a production-ready, mise-based GitLab CI/CD pipeline including unit tests, linting, optional coverage reporting, snapshot builds, and automated releases.
Why This Skill Exists
Problem: Setting up GitLab CI/CD for Go projects requires manually creating pipeline configuration, understanding GitLab CI syntax, and keeping tool versions in sync between local development and CI - a 30-45 minute process.
Solution: One-command generation that:
- Creates a complete
.gitlab-ci.ymlconfiguration (mise-based) - Runs every job in the
jdx/mise:latestimage, installs tools viamise install, then runstask …— so CI uses the exact versions pinned inmise.toml - Ensures a
mise.tomlexists at the repo root (creates one with detected versions if missing) — the single source of truth shared with local dev - Includes a pipeline: unit tests, linter, snapshot builds, releases (+ optional coverage)
- Keeps Docker-in-Docker image publishing as a clearly-marked optional block
- Preserves all customization comments for user control
Content Generation Rules
CRITICAL: When generating any content (pipeline files, 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 (6 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 skill is for Go projects only."
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.
- 22d ago First seen · 506 lines · 24 tokens per session scan A 13bb234190b8
gen-gitlab-ci is a skill published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 8d ago), licensed MIT. It adds 24 tokens to every session and 4,794 once invoked, about $0.0001 per session on Opus 5.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-25.
Other skills, from other repositories
implementing-go
Implements concise, streamlined Go code matching exact architect specifications. Use when writing Go code, creating packages, or when the user asks to implement features in Go.
reviewing-go
Provides concise, focused Go code reviews matching exact task complexity requirements. Use when reviewing Go code quality, concurrency safety, or when the user asks for code review.
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…
tree-sitter-language-pack-managing-parsers
Use when the user needs to manage the tree-sitter parser cache — prefetch parsers for offline or CI runs, list what is downloaded, inspect a language, find the cache directory, or clean it. Covers ts-pack download, list, info, cache-dir, clean, and init.
dotnet-analyzers
Run dotnet format to fix code style and analyzer diagnostics (IDE0005, CA, SA). Use when fixing unnecessary usings, code style violations, analyzer warnings, or verifying format compliance.
dotnet-dependency
This skill should be used when investigating .NET project dependencies, understanding why packages are included, listing references, or auditing for outdated/vulnerable packages.