GitOps with ArgoCD and Flux
wshobson/agents
Sets up GitOps continuous delivery for Kubernetes with ArgoCD or Flux, covering installation, repository layout, sync policies, progressive delivery and secrets.
Add, configure, or modify GitOps addons on the PEEKS platform.
Install Manage Addons
$ npx skills add aws-samples/appmod-blueprints --skill manage-addons -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aws-samples/appmod-blueprints manage-addons --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/aws-samples/appmod-blueprints.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.kiro/skills/manage-addons .claude/skills/manage-addons && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "manage-addons" agent skill from https://github.com/aws-samples/appmod-blueprints/tree/main/.kiro/skills/manage-addons into .claude/skills/manage-addons/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-addons", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/aws-samples/appmod-blueprints/tree/main/.kiro/skills/manage-addonsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add aws-samples/appmod-blueprints --skill manage-addons -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aws-samples/appmod-blueprints manage-addons --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws-samples/appmod-blueprints.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.kiro/skills/manage-addons .agents/skills/manage-addons && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "manage-addons" agent skill from https://github.com/aws-samples/appmod-blueprints/tree/main/.kiro/skills/manage-addons into .agents/skills/manage-addons/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-addons", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aws-samples/appmod-blueprints --skill manage-addons -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aws-samples/appmod-blueprints manage-addons --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws-samples/appmod-blueprints.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.kiro/skills/manage-addons .cursor/skills/manage-addons && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "manage-addons" agent skill from https://github.com/aws-samples/appmod-blueprints/tree/main/.kiro/skills/manage-addons into .cursor/skills/manage-addons/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-addons", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/aws-samples/appmod-blueprints.git --path .kiro/skills/manage-addons--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add aws-samples/appmod-blueprints --skill manage-addons -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aws-samples/appmod-blueprints manage-addons --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws-samples/appmod-blueprints.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.kiro/skills/manage-addons .gemini/skills/manage-addons && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "manage-addons" agent skill from https://github.com/aws-samples/appmod-blueprints/tree/main/.kiro/skills/manage-addons into .gemini/skills/manage-addons/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-addons", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install aws-samples/appmod-blueprints manage-addonsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add aws-samples/appmod-blueprints --skill manage-addons -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aws-samples/appmod-blueprints.git skills-src && mkdir -p .github/skills && cp -r skills-src/.kiro/skills/manage-addons .github/skills/manage-addons && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "manage-addons" agent skill from https://github.com/aws-samples/appmod-blueprints/tree/main/.kiro/skills/manage-addons into .github/skills/manage-addons/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-addons", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aws-samples/appmod-blueprints --skill manage-addons -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aws-samples/appmod-blueprints manage-addons --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws-samples/appmod-blueprints.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.kiro/skills/manage-addons .opencode/skills/manage-addons && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "manage-addons" agent skill from https://github.com/aws-samples/appmod-blueprints/tree/main/.kiro/skills/manage-addons into .opencode/skills/manage-addons/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-addons", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
manage-addons- GitHub stars
- 113
- Token cost
- ~1k tokens
- SKILL.md length
- 422 words
- Files
- 3 (incl. references)
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- MIT-0
At a glance
Add, configure, or modify GitOps addons on the PEEKS platform.
- Works in 5 steps: Understand the GitOps Architecture → Add a New Addon → Configure Addon Values → …
- Adding a new addon
- SKILL.md covers Overview, Parameters and Workflow
- Calls terraform and yq
What it does
Manage Addons is an agent skill from aws-samples/appmod-blueprints, published by the product's own GitHub organization. Add, configure, or modify GitOps addons on the PEEKS platform. Use when adding a new addon, enabling an addon on a cluster, configuring addon values, troubleshooting addon deployment, or editing addon enablement (enabled-addons.yaml). Do NOT use for general kubectl troubleshooting — use troubleshoot-platform instead.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/sync-waves.md` and `references/values-separation.md`).
It sits in DevOps & Cloud, covering GitOps, Container orchestration and Deployment. It works with Kubernetes. The licence is MIT-0.
When your agent uses it
- Adding a new addon
- Enabling an addon on a cluster
- Configuring addon values
- Troubleshooting addon deployment
Example prompts
- “/manage-addons”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 42ea29c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
terraformyq
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Manage Addons loads about 1k tokens when it runs, and up to ~1.6k if it reads all its reference files. Until then it costs about 84 tokens; SKILL.md has 422 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from aws-samples/appmod-blueprints at commit 42ea29c, republished under its MIT-0 licence (© aws-samples). 422 words, ~1,021 tokens.
Download SKILL.mdSave it as
.claude/skills/manage-addons/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- manage-addons
- description
- Add, configure, or modify GitOps addons on the PEEKS platform. Use when adding a new addon, enabling an addon on a cluster, configuring addon values, troubleshooting addon deployment, or editing addon enablement (`enabled-addons.yaml`). Do NOT use for general kubectl troubleshooting — use troubleshoot-platform instead.
Manage Addons
Overview
Guides the proper GitOps workflow for adding, enabling, and configuring platform addons deployed via ArgoCD ApplicationSets.
Parameters
- operation (required): "add", "enable", "configure", or "debug"
- addon_name (required): Name of the addon (kebab-case)
- cluster_name (optional): Target cluster (hub, spoke-dev, spoke-prod)
Workflow
1. Understand the GitOps Architecture
The platform uses a three-tier configuration system:
| Layer | File | Purpose |
|---|---|---|
| Addon registry | gitops/addons/registry/<domain>.yaml | Central registry of all addons (core, platform, security, observability, ml, gitops) |
| Environment enablement | gitops/overlays/environments/<env>/enabled-addons.yaml | Per-environment enablement (source of truth for cluster secret enable_* labels) |
| Value overlays | gitops/overlays/environments/<env>/<addon>/values.yaml | Per-environment/cluster value overrides |
Constraints:
- You MUST prefer GitOps workflow (modify Git → commit → push → ArgoCD sync) over manual kubectl apply because manual changes drift from Git state
- You MUST NOT manually modify cluster secrets — always update through
gitops/overlays/environments/<env>/enabled-addons.yamlbecause the fleet-secret chart generates these labels from it - Read-only kubectl operations (get, describe, logs) are allowed without confirmation
2. Add a New Addon
Constraints:
- You MUST add the addon entry in the appropriate
gitops/addons/registry/<domain>.yamlwith selector and valuesObject - You MUST add
enable_<addon>: falseto the relevantgitops/overlays/environments/<env>/enabled-addons.yaml - You MUST choose an appropriate sync wave based on dependencies (see references/sync-waves.md)
- You MUST NOT put dynamic template values (
{{.metadata.annotations.*}}) in values.yaml files because they will be overridden — see references/values-separation.md - You SHOULD create a values overlay at
gitops/addons/default/addons/<addon>/values.yamlfor static config - You SHOULD apply changes via GitOps (commit → push → ArgoCD sync); use
task installfor provider bootstrap, never rawterraform apply
Show full SKILL.md (189 more words)Show less
3. Configure Addon Values
See references/values-separation.md for the dynamic vs static values pattern.
Constraints:
- You MUST keep dynamic template values ONLY in
addons.yamlvaluesObject - You MUST NOT use empty strings for dynamic values in values.yaml because they override templates
- You SHOULD validate YAML after modifications:
yq eval '.' <file> > /dev/null
4. Configure HA for Critical Addons
Constraints:
- You MUST configure 2+ replicas for critical services (hub, proxy, controller)
- You MUST add PodDisruptionBudgets with
maxUnavailable: 1 - You MUST configure topologySpreadConstraints for multi-AZ distribution
- You MUST set memory limits equal to requests for critical components because this prevents OOM kills
- You MUST NOT set CPU limits on critical components because it causes throttling
- You SHOULD use system nodeSelector and CriticalAddonsOnly tolerations
5. Debug Addon Deployment
If an addon is not deploying:
- Check cluster secret has
enable_<addon>: "true"label - Check
addons.yamlhasenabled: truefor the ApplicationSet - Verify template resolution — check cluster secret annotations
- Check ArgoCD Application events for sync errors
Constraints:
- You MUST distinguish between
enabled(ApplicationSet creation) andenable_<addon>(cluster targeting) because they are different mechanisms - You MUST check sync wave dependencies if addon fails to deploy
© aws-samples, MIT-0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in .kiro/skills/manage-addons of aws-samples/appmod-blueprints.
- SKILL.md
- references/sync-waves.md
- references/values-separation.md
Open the folder on GitHubat commit 42ea29c
Compare with similar skills
Manage Addons next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Manage Addons this skillaws-samples/appmod-blueprints | 113 | — | ~1k | Automated safety check: Pass | MIT-0 | |
| GitOps with ArgoCD and Fluxwshobson/agents | 40k | 12 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Devops EngineerYikai-Liao/symusic | 189 | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Deploying Applicationsancoleman/ai-design-components | 526 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Implementing Gitopsancoleman/ai-design-components | 526 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Devops Excellencemajiayu000/spellbook | 286 | — | ~2.4k | Automated safety check: Notes | MIT |
Similar skills
Devops Engineer
Yikai-Liao/symusic
Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates.
Deploying Applications
ancoleman/ai-design-components
Deployment patterns from Kubernetes to serverless and edge functions.
Implementing Gitops
ancoleman/ai-design-components
Implement GitOps continuous delivery for Kubernetes using ArgoCD or Flux.
Devops Excellence
majiayu000/spellbook
DevOps and CI/CD expert. An agent skill from majiayu000/spellbook.
Deployment Engineer
Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI
MASTER DEPLOY: CI/CD Pipelines, Docker, K8s, GitOps. An agent skill from Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI.
More from aws-samples/appmod-blueprints
All 9 skills in this repo- Official
Eks Best Practices
aws-samples/appmod-blueprints
Advisory guidance for Amazon EKS architecture and configuration decisions — compute strategy, networking, security, reliability, cost, autoscaling, observability, multi-tenancy, and upgrade planning.
- Official
Troubleshoot Platform
aws-samples/appmod-blueprints
Systematic troubleshooting for the PEEKS workshop platform — EKS clusters, Terraform state, ingress, load balancers, MCP tool failures, YAML validation.
- Official
Eks Recon
aws-samples/appmod-blueprints
EKS cluster reconnaissance and environment discovery. An agent skill from aws-samples/appmod-blueprints.
- Official
Troubleshoot Kro
aws-samples/appmod-blueprints
Troubleshoot Kro ResourceGraphDefinition (RGD) issues — stuck instances, ACK resource failures, IAM trust policy problems, resource conflicts.
- Official
Eks Upgrade Check
aws-samples/appmod-blueprints
Assess EKS cluster upgrade readiness — run automated checks across 8 areas (version, breaking changes, deprecated APIs, add-on compatibility, node readiness, workload risks, AWS Insights, upgrade…
- Official
Eks Platform Engineering
aws-samples/appmod-blueprints
A skill your agent uses whenever someone is designing or building an Internal Developer Platform (IDP) or doing platform engineering on Amazon EKS — phrased as "build a developer platform"…
Related
Works with
Categories
Questions about Manage Addons
What does Manage Addons do?
Add, configure, or modify GitOps addons on the PEEKS platform. Manage Addons is an agent skill from aws-samples/appmod-blueprints, published by the product's own GitHub organization. Add, configure, or modify GitOps addons on the PEEKS platform.
When should I use Manage Addons?
Manage Addons fits situations like: adding a new addon; enabling an addon on a cluster; configuring addon values; troubleshooting addon deployment.
How do I install Manage Addons in Claude Code?
Run `npx skills add aws-samples/appmod-blueprints --skill manage-addons -a claude-code`. Or copy the skill folder (.kiro/skills/manage-addons in aws-samples/appmod-blueprints) into .claude/skills/manage-addons in your project. Claude Code loads it when a task matches its description.
How do I install Manage Addons in Codex?
Run `npx skills add aws-samples/appmod-blueprints --skill manage-addons -a codex`. Or copy the skill folder (.kiro/skills/manage-addons in aws-samples/appmod-blueprints) into .agents/skills/manage-addons in your project. Codex loads it when a task matches its description.
Can I use Manage Addons in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aws-samples/appmod-blueprints --skill manage-addons -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/manage-addons, .gemini/skills/manage-addons, .github/skills/manage-addons and .opencode/skills/manage-addons in your project.
What does Manage Addons need to run?
Going by SKILL.md and its folder, Manage Addons needs the command-line tools its instructions call (terraform and yq).
Does Manage Addons access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Manage Addons safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Manage Addons use?
Manage Addons is published under the MIT-0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Manage Addons use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 608 tokens, read only when the agent opens those files.
What are the alternatives to Manage Addons?
Skills that share tags, products or a category with Manage Addons: GitOps with ArgoCD and Flux (wshobson/agents, 40k stars), Devops Engineer (Yikai-Liao/symusic, 189 stars), Deploying Applications (ancoleman/ai-design-components, 526 stars) and Implementing Gitops (ancoleman/ai-design-components, 526 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Manage Addons?
aws-samples (a GitHub organization, an official publisher) maintains it in aws-samples/appmod-blueprints, which has 113 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 7, 2026.
Source: aws-samples/appmod-blueprints on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.