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 j4flmao/agent-skills --skill gitops-workflowsgit clone --depth 1 https://github.com/j4flmao/agent-skillsWrote 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/j4flmao/agent-skills/gitops-workflows)<a href="https://agentmods.dev/skills/j4flmao/agent-skills/gitops-workflows"><img src="https://agentmods.dev/badge/skills/j4flmao/agent-skills/gitops-workflows/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/j4flmao/agent-skills/gitops-workflows"><img src="https://agentmods.dev/badge/skills/j4flmao/agent-skills/gitops-workflows.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.00000 | $0.00414 |
| Opus 5 | $0.00000 | $0.00207 |
| Sonnet 5 | $0.00000 | $0.00083 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
gitops-workflows 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 8d 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.
What it actually says
GitOps Workflows & Progressive Delivery
1. Skill Context
Focus: ArgoCD, FluxCD, declarative infrastructure, secrets management, and progressive delivery (Canary/Blue-Green). Triggers: argocd setup, gitops workflow, multi-cluster gitops, manage secrets gitops, progressive delivery
2. Deep GitOps Mechanics
The agent must treat Git as the absolute source of truth for the entire Kubernetes state.
Multi-Environment Synchronization
- App of Apps Pattern (ArgoCD): Managing a root application that recursively deploys other applications to bootstrap entire clusters from scratch.
- Branching Strategies: Environment-per-branch (legacy) vs Environment-per-folder (recommended). Promoting configurations via Pull Requests from
overlays/stagingtooverlays/production.
Managing Secrets in GitOps
- The Problem: Committing raw Kubernetes Secrets to Git is a critical security vulnerability.
- Solutions:
- Sealed Secrets (Bitnami): Asymmetric encryption where the public key encrypts the manifest, and only the cluster holds the private decryption key.
- External Secrets Operator (ESO): GitOps manages the reference to a secret in AWS Secrets Manager / HashiCorp Vault. The operator fetches the real value and injects it into a native K8s Secret at runtime.
Progressive Delivery
- Flagger / Argo Rollouts: Moving beyond basic Rolling Updates. Incrementally shifting traffic (e.g., 5%, 10%, 50%) to the new version using an Ingress Controller/Service Mesh (Istio, Nginx) while continuously querying Prometheus metrics to ensure the new version is healthy before proceeding.
3. Output Format
- Provide Kustomize or Helm directory structures for multi-env GitOps.
- Output ArgoCD
ApplicationorApplicationSetYAMLs. - Explain the reconciliation loop and drift detection mechanisms.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 27 lines · 0 tokens per session scan A 0ddd7b43cdc4
gitops-workflows is a skill published in the GitHub repository j4flmao/agent-skills (23 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 414 tokens. 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
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. (gstack).
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
releasepr
Adopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication. Excludes pr-release internals and general versioning advice.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
seed-snapshot-release
An automated workflow for creating and tracking a snapshot release of the pull request on the current branch. A snapshot release is a temporary package build used for testing a branch before a normal release.