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 aws-cicd-authgit 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/aws-cicd-auth)<a href="https://agentmods.dev/skills/atretyak1985/swarmery/aws-cicd-auth"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/aws-cicd-auth/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/aws-cicd-auth"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/aws-cicd-auth.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.00050 | $0.04721 |
| Opus 5 | $0.00025 | $0.02361 |
| Sonnet 5 | $0.00010 | $0.00944 |
| Haiku 4.5 | $0.00005 | $0.00472 |
Grade A, and why
aws-cicd-auth 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 7d 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 — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Define, configure, and review how the project's GitHub Actions workflows authenticate to AWS to push container images and trigger deployments. The pattern is keyless OIDC — GitHub Actions exchanges a short-lived OIDC token for temporary AWS STS credentials by assuming an IAM role. No long-lived AWS access keys are stored anywhere (not in repo secrets, not in ~/.aws). The only secrets stored are non-sensitive identifiers (role ARN, region, repo/cluster/service names).
The reference implementation is the API repo's (project.json → mainApp) .github/workflows/deploy-prod.yml: it assumes an IAM role via aws-actions/configure-aws-credentials@v4, logs into Amazon ECR, builds/pushes the image, and forces a new Amazon ECS deployment.
When to use
- Setting up AWS auth for a new repo or service in the project that needs to push to ECR / deploy to ECS from GitHub Actions.
- Reviewing an existing OIDC auth stanza (
permissions: id-token: write,configure-aws-credentials, role ARN scoping). - Authoring or auditing the IAM trust policy (who can assume the CI role — the
sub/audconditions). - Authoring or auditing the IAM permission policy (what the CI role can do — ECR push + ECS deploy, least-privilege).
- Debugging an auth failure:
Error: Could not assume role,Not authorized to perform sts:AssumeRoleWithWebIdentity, ECRdenied, ECSAccessDenied. - Adding a new repo/service to the existing OIDC pattern.
When NOT to use
- Overall CI/CD pipeline structure (job/stage ordering,
workflow_runtriggers, concurrency, build matrix) — usegithub-actions-cicd. - Docker image build/tag/push mechanics (Dockerfile, layer caching, tag strategy) — use
docker-build. - Application-level AWS IAM, Cognito, runtime task-role permissions the app uses at runtime, or end-user auth — out of scope (this skill is CI identity only).
- GCP / any non-AWS cloud — this skill is AWS-only; for GCP CI auth use
gcp-cicd-auth.
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.
- 7d ago First seen · 334 lines · 50 tokens per session scan A a0d92878c32a
aws-cicd-auth is a skill published in the GitHub repository atretyak1985/swarmery (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 50 tokens to every session and 4,721 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
devops-cloud
DevOps, cloud infrastructure, and platform engineering. Use when working with AWS, GCP, Azure, Kubernetes, Terraform, CI/CD pipelines, or infrastructure as code.
hr-devops
Help HR managers, recruiters, and talent acquisition teams understand DevOps, Platform Engineering, Site Reliability Engineering (SRE), cloud infrastructure, CI/CD, and modern software delivery workflows. Use when asked to explain DevOps, screen DevOps candidates, understand CI/CD, compare DevOps and SRE, evaluate…
tailscale
This skill should be used when managing Tailscale mesh VPN networks. Use when the user asks to "check tailscale status", "list tailscale devices", "ping a device", "send file via tailscale", "tailscale funnel", "tailscale serve", "create auth key", "check who's online", "tailscale exit node", "Magic DNS", or mentions…
railway
Railway allows you to deploy code simply by pushing to GitHub or using the CLI. The Railway Public API (GraphQL) allows programmatic management of projects, environments, and deployments.
define-slo-sli-sla
Establish Service Level Objectives (SLO), Service Level Indicators (SLI), and Service Level Agreements (SLA) with error budget tracking, burn rate alerts, and automated reporting using Prometheus and tools like Sloth or Pyrra. Use when defining reliability targets for customer-facing services, balancing feature…
gws-script
Apps Script: Deploy and manage Google Apps Script projects with gws script +push.