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 agentmods add skills/aidas-dev/k8s-agent-skills/flaggernpx skills add Aidas-dev/k8s-agent-skills --skill flaggergit clone --depth 1 https://github.com/Aidas-dev/k8s-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/aidas-dev/k8s-agent-skills/flagger)<a href="https://agentmods.dev/skills/aidas-dev/k8s-agent-skills/flagger"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/flagger.svg" alt="Measured on agentmods" 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.02908 |
| Opus 5 | $0.00000 | $0.01454 |
| Sonnet 5 | $0.00000 | $0.00582 |
| Haiku 4.5 | $0.00000 | $0.00291 |
Grade A, and why
flagger 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 5d 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 — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flagger
Overview
Flagger automates progressive delivery for Kubernetes workloads. It gradually shifts traffic to a new version while measuring metrics and running conformance tests. Supports canary releases (weighted traffic), A/B testing (header/cookie routing), and blue/green deployments (instant switch or mirroring).
CRDs: Canary (flagger.app/v1beta1), MetricTemplate, AlertProvider.
Latest: chart 1.43.0, app v1.43.0 (Apr 2026).
Architecture
User creates/updates Canary resource
→ Flagger creates:
- <name>-primary Deployment (stable version)
- <name>-canary Deployment (new version)
- <name> ClusterIP service (routes to primary)
- <name>-primary ClusterIP service (stable)
- <name>-canary ClusterIP service (new)
- Mesh/Ingress routing objects (if mesh provider set)
→ Analysis loop:
1. Increment traffic to canary (stepWeight)
2. Run webhooks (pre-rollout, rollout, post-rollout)
3. Check metrics (success rate, duration, custom)
4. If all pass → promote canary to primary
5. If threshold exceeded → rollback
CRD: Canary
apiVersion: flagger.app/v1beta1, kind: Canary
Minimal Example (Kubernetes CNI — no mesh)
apiVersion: flagger.app/v1beta1
kind: Canary
metadata:
name: myapp
namespace: prod
spec:
provider: kubernetes # No service mesh (uses ClusterIP + pod labels)
targetRef:
apiVersion: apps/v1
kind: Deployment
name: myapp
service:
port: 9898
portDiscovery: true
analysis:
interval: 1m
threshold: 5
iterations: 10 # Used for blue/green with no mesh provider
metrics:
- name: request-success-rate
thresholdRange:
min: 99
interval: 1m
webhooks:
- name: load-test
type: rollout
url: http://flagger-loadtester.test/
metadata:
cmd: "hey -z 1m -q 10 http://myapp-canary.prod:9898/"
CanarySpec Fields
| Field | Required | Description |
|---|---|---|
provider |
Yes | Traffic provider: kubernetes, istio, linkerd, nginx, contour, gloo, traefik, gatewayapi:v1, apisix, kuma, knative, skipper, osm, smi:v1alpha2, appmesh:v1beta2 |
targetRef |
Yes | Target Deployment reference |
autoscalerRef |
No | HPA reference (copied to canary) |
service |
Yes | Service spec (port, portName, targetPort, hosts, gatewayRefs, match, rewrite, timeout, headers, etc.) |
suspend |
No | Suspend all canary runs |
progressDeadlineSeconds |
No | Max time for canary progress before rollback (default 600) |
skipAnalysis |
No | Promote without analysis (default false) |
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.
- 5d ago First seen · 293 lines · 0 tokens per session scan A 99b219ca26ca
flagger is a skill published in the GitHub repository Aidas-dev/k8s-agent-skills (2 stars, last pushed 22d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,908 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-08-31.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…