agentmods.dev

gen-gitlab-ci

gen-gitlab-ci is a command for coding agents from sgaunet/claude-plugins. It costs 24 tokens per session (4,788 once invoked), scanned A, original, MIT.

A command that creates a GitLab CI/CD configuration for Go projects. GitLab CI/CD automatically builds and tests code when changes are made.

In plain words
What is it for?
Use it to generate jobs for unit tests, linting, optional coverage reports, snapshot builds, and automated releases, with an optional image-publishing section.
Why use it?
It removes the need to write the pipeline configuration by hand and keeps local tool versions aligned with the versions used in automated builds.

Command

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the go-specialist plugin — 4 skills, 7 commands, 1 agent shipped together

not rated 16 9d ago A scan 24 tokens original MIT
View the source file sgaunet/claude-plugins
Install

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.

agentmods
npx agentmods add commands/sgaunet/claude-plugins/gen-gitlab-ci
Clone the repo
git clone --depth 1 https://github.com/sgaunet/claude-plugins

Or install go-specialist, the plugin that ships this one along with the rest of its 4 skills, 7 commands, 1 agent.

Wrote 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.

agentmods badge for gen-gitlab-ci

README.md
[![agentmods](https://agentmods.dev/badge/commands/sgaunet/claude-plugins/gen-gitlab-ci.svg)](https://agentmods.dev/commands/sgaunet/claude-plugins/gen-gitlab-ci)
Your own site
<a href="https://agentmods.dev/commands/sgaunet/claude-plugins/gen-gitlab-ci"><img src="https://agentmods.dev/badge/commands/sgaunet/claude-plugins/gen-gitlab-ci.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,788 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00024 $0.04788
Opus 5 $0.00012 $0.02394
Sonnet 5 $0.00005 $0.00958
Haiku 4.5 $0.00002 $0.00479

Measured 3d ago against content hash 7caf100fcc61, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 3d 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.

plugins/go-specialist/commands/gen-gitlab-ci.md · 504 lines

How it starts

The opening of the file, as written. The whole thing — 504 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Generate GitLab CI Configuration Command

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 Command 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.yml configuration (mise-based)
  • Runs every job in the jdx/mise:latest image, installs tools via mise install, then runs task … — so CI uses the exact versions pinned in mise.toml
  • Ensures a mise.toml exists 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:

  1. Validate Git repository:

    git rev-parse --git-dir
    • If fails: Exit with error "Not a git repository. Run 'git init' first."

  2. Validate Go project:

    test -f go.mod
    • If fails: Exit with error "go.mod not found. This command is for Go projects only."

Read the full file on GitHub · 504 lines

Changes

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.

  1. 3d ago First seen · 504 lines · 24 tokens per session scan A 7caf100fcc61

Subscribe to this mod's changes

gen-gitlab-ci is a command published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 9d ago), licensed MIT. It adds 24 tokens to every session and 4,788 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.

CI and CDDevOps and cloudGoLanguagesai-agentsclaude-codeclaude-code-marketplaceclaude-code-pluginsdeveloper-tools
Related

Other commands, from other repositories

plan-launch

Plan a full go-to-market launch — positioning, messaging hierarchy, ICP definition, launch timeline, rollback plan, and post-launch measurement.

Productfculty-aipm/PM-Copilot-by-Product-Faculty · 26 tokens

battlecard

Create a sales-ready competitive battlecard — positioning, feature comparison, objection handling, and win strategies.

phuryn/pm-skills · 19 tokens

cli-patterns

Reference patterns for implementing CLI commands in internal/cli/.

nylas/cli · 0 tokens

bootstrap

Scaffold test, lint, and CI infrastructure for projects that lack it.

Joncik91/ucai · 14 tokens

ideal-customer-profile

Build, enrich, or audit your ICP — trigger events, buyer map, JTBD, disqualifiers.

stefanoskarakasis/Product-Marketing-Skills · 21 tokens

privacy

Draft a jurisdiction-aware privacy policy for a digital product.

stefanoskarakasis/Product-Marketing-Skills · 10 tokens