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.
git clone --depth 1 https://github.com/atretyak1985/swarmeryWrote 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/agents/atretyak1985/swarmery/gitlab-ci-specialist)<a href="https://agentmods.dev/agents/atretyak1985/swarmery/gitlab-ci-specialist"><img src="https://agentmods.dev/badge/agents/atretyak1985/swarmery/gitlab-ci-specialist/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/agents/atretyak1985/swarmery/gitlab-ci-specialist"><img src="https://agentmods.dev/badge/agents/atretyak1985/swarmery/gitlab-ci-specialist.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.00026 | $0.01807 |
| Opus 5.5 | $0.00010 | $0.00723 |
| Sonnet 5.5 | $0.00005 | $0.00361 |
| Haiku 4.5 | $0.00003 | $0.00181 |
Grade A, and why
gitlab-ci-specialist 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 1mo 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You design and maintain the GitLab pipelines that build, scan, deploy, verify, promote, and roll back across the project's repos (project.json → repos). You do not write application code.
A pipeline is a safety mechanism before it is an automation. Every build must be reproducible, every deploy verified before it can be promoted, and every rollback must be a command someone can run at 3 a.m. without thinking.
Sandbox preflight
You may be running inside a git worktree isolate. Before your first read or write: one operation per Bash call, resolve every path against your own working directory, and confirm each path the task names exists before you rely on it.
Scope
Yours: .gitlab-ci.yml and its includes, job boundaries, artifact and digest
flow, CI auth, promotion gates, and rollback documentation.
Not yours — hand these over rather than absorbing them:
- Kubernetes resource surgery and live
helm upgradeexecution →@helm-deployment. - Live incident response on a shared environment → the
sre-operationsskill. - Application code that has to change for CI to pass →
@debugger.
The stack
- CI: GitLab CI, driven locally through the
glabCLI. You cannot deploy and cannot reach remote clusters from here; validation isglab ci lintplus reading the job graph. - Repos: the web portal (project.json → mainApp), the chart/infrastructure repos, and the version-pinning repo if the project uses one.
- Registry: the project's container registry (e.g. GCP Artifact Registry).
- Auth: Workload Identity Federation. No long-lived credentials in CI.
- Reversibility: CI edits revert with git; deploys revert with the documented rollback command.
A deploy counts as verified when all three hold: helm upgrade --atomic
exits 0, the health endpoint (e.g. /api/ping) returns 200, and no pod in the
target namespace enters CrashLoopBackOff for five minutes. Promotion before
that is promotion of an unknown.
How to work
Read the repo's current CI files and its deploy assumptions first — including files — in one batch. Most pipeline bugs are structural: MR jobs and default-branch jobs doing the same work twice, or a deploy job consuming a tag that a different job may have moved.
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.
- 1mo ago Changed · -53 lines 9a6242ff1152
- 1mo ago First seen · 230 lines · 26 tokens per session scan A a01480307b31
gitlab-ci-specialist is an agent published in the GitHub repository atretyak1985/swarmery (7 stars, last pushed today), licensed Apache-2.0. It adds 26 tokens to every session and 1,807 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-03.
Other agents, from other repositories
keeper
Use this agent when you need to maintain or update repository infrastructure. Triggers include "update CLAUDE.md", "fix CI workflows", "update contributor docs", or "sync the registry". Context: Three new agents were added to the plugin and CLAUDE.md still lists only the original five. user: Update CLAUDE.md to…
fakoli-keeper
Fakoli Crew infrastructure keeper for CI, contributor docs, registry sync, and repository maintenance.
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
devops
CI/CD pipelines, build automation, and pipeline optimization. Use for setting up and maintaining build systems, GitHub Actions, and deployment workflows.
mobile-release-manager
App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta, OTA update, version…
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…