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 skills add atretyak1985/swarmery --skill gitops-promotiongit 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/skills/atretyak1985/swarmery/gitops-promotion)<a href="https://agentmods.dev/skills/atretyak1985/swarmery/gitops-promotion"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/gitops-promotion/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/atretyak1985/swarmery/gitops-promotion"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/gitops-promotion.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.00067 | $0.04057 |
| Opus 5 | $0.00034 | $0.02028 |
| Sonnet 5 | $0.00013 | $0.00811 |
| Haiku 4.5 | $0.00007 | $0.00406 |
Grade A, and why
gitops-promotion 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 6d 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Define and enforce the GitOps promotion flow for the project's Wave B deployment model, where a pull-based controller (Flux or ArgoCD) reconciles the cluster from the version-pinning repo's desired state (project.json → repos; referenced below as <versions-repo>). Covers the boundary between Wave A (GitLab-native imperative deploy) and Wave B (GitOps pull-based), promotion sequencing, rollback via Git, and verification gates.
When to use this skill (triggers)
- Configuring or reviewing the GitOps promotion flow after a pull-based controller is deployed
- Updating
<versions-repo>desired-state files for candidate, current, or previous digests - Designing the verify-then-promote gate in a GitOps workflow
- Rolling back a deployment by updating desired state to a previous digest
- Determining whether a task belongs in Wave A (imperative) or Wave B (GitOps)
Only activate if a GitOps controller (Flux v2 or ArgoCD) is confirmed deployed in the target cluster.
When NOT to use this skill (anti-triggers)
- Wave A imperative deployments where GitLab CI runs
helm upgradedirectly -- usegitlab-ci-cd - CI pipeline structure (stages, rules, artifacts) -- use
gitlab-ci-cdeven in Wave B (CI still builds/scans/publishes) - Helm chart template authoring or values configuration -- use
helm-chart-expert - GCP authentication for image push or secret access -- use
gcp-cicd-auth - No GitOps controller is deployed yet -- this skill produces guidance that cannot be acted on without a controller; redirect to
gitlab-ci-cd
Required environment (Runtime: .claude/skills/gitops-promotion/SKILL.md)
- Tools/libraries: Read (inspect desired-state files), Grep (search for digest references), Edit (update desired state), Bash (run detection commands)
- Prerequisite: a pull-based GitOps controller (Flux v2 or ArgoCD) is deployed in the target cluster
Inputs
action: string--promote(advance candidate to current),rollback(revert to previous), orreview(audit the current flow)environment: string-- target environment (<envAlias>staging,staging,production)digest: string(optional) -- specific image digest for promote/rollback
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.
- 6d ago First seen · 294 lines · 67 tokens per session scan A ad88d1d7fc26
gitops-promotion is a skill published in the GitHub repository atretyak1985/swarmery (5 stars, last pushed today), licensed Apache-2.0. It adds 67 tokens to every session and 4,057 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-09-03.
Other skills, from other repositories
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
release-notes
Draft short release notes from a list of changes. Use when the user asks for changelogs, release notes, or a concise product update.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
release-notes
Create release notes for a new version tag. Gathers all commits, PRs, issues fixed, and breaking changes since a previous release. Creates the release notes markdown file, tags the repo, and pushes. Asks the user to confirm the base version to diff against.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.