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 github-actions-cicdgit 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/github-actions-cicd)<a href="https://agentmods.dev/skills/atretyak1985/swarmery/github-actions-cicd"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/github-actions-cicd.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.00078 | $0.05691 |
| Opus 5 | $0.00039 | $0.02846 |
| Sonnet 5 | $0.00016 | $0.01138 |
| Haiku 4.5 | $0.00008 | $0.00569 |
Grade A, and why
github-actions-cicd 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 — 419 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Author, review, and debug the GitHub Actions workflows that drive the project's repositories. Produce workflow YAML that matches the established CI job graph, the AWS ECR/ECS deploy contract, and the standardized workflow set each repo ships — so a workflow in any repo is recognizable from any other.
Read the project's shape from project.json (repos/monorepo) — this skill covers both; the examples below use a multi-repo layout. Each repository owns its own .github/workflows/ directory and runs the same standardized set of workflows. The application repos (e.g. the API repo — project.json → mainApp — a NestJS service, plus the client/admin/vendor/mobile repos) build container images; the infrastructure repo carries its own ci.yml + deploy.yml.
Cloud is AWS — images go to ECR, services run on ECS with a rolling, force-new-deployment update. There is no GCP, no Kubernetes, no Helm, and no GitOps controller anywhere in this pipeline. Deploys are imperative aws ecs update-service calls followed by a stability poll.
When to use
- Adding or modifying a job in a repo's
ci.yml(type-check, lint, test, build, security, summary). - Writing or fixing the ECR build/push + ECS force-new-deployment flow in
deploy-prod.yml. - Bringing a repo's workflow set in line with the standard (
ci.yml,deploy-prod.yml,nightly.yml,version-bump.yml,secret-scan.yml,dependabot-lockfix.yml,branch-protection.yml). - Debugging a failing Actions run — a red CI job, a deploy that never reaches ECS stability, a
workflow_runtrigger that didn't fire. - Tuning concurrency,
permissions, the Node/service-container matrix, or the$GITHUB_STEP_SUMMARYaggregation. - Reviewing a PR that touches any file under
.github/workflows/.
When NOT to use
- AWS OIDC trust, the assumed IAM role, ECR repository permissions, or the
AWS_ROLE_ARNfederation setup — useaws-cicd-auth. This skill consumes those secrets; it does not define the cloud-side trust. - Dockerfile authoring or image-build mechanics (layer caching, build args, multi-stage, image size) — use
docker-build. This skill only invokesdocker build/docker push; it does not own the Dockerfile. - ECS task definition / service / cluster provisioning (infrastructure-as-code) — out of scope; the workflow assumes the cluster and service already exist.
- Application code, tests, or lint rules themselves — this skill wires the commands (
npm run typecheck,npm run test:cov), it does not write them. - Prometheus/Grafana CI metrics — use
monitoring.
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 · 419 lines · 78 tokens per session scan A d4a09d0b2a9a
github-actions-cicd is a skill published in the GitHub repository atretyak1985/swarmery (4 stars, last pushed today), licensed Apache-2.0. It adds 78 tokens to every session and 5,691 once invoked, about $0.0004 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.