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 supply-chain-securitygit 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/supply-chain-security)<a href="https://agentmods.dev/skills/atretyak1985/swarmery/supply-chain-security"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/supply-chain-security/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/supply-chain-security"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/supply-chain-security.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.00052 | $0.00815 |
| Opus 5.5 | $0.00021 | $0.00326 |
| Sonnet 5.5 | $0.00010 | $0.00163 |
| Haiku 4.5 | $0.00005 | $0.00081 |
Grade A, and why
supply-chain-security 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 1mo 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Audit the container image lifecycle — build through promotion — against four baseline controls (image scanning, SBOM generation, immutable digest promotion, rollback retention) and two roadmap controls (image signing, provenance attestation), producing a gap report with current-state assessments and prioritized remediation. Application code vulnerabilities belong to security-audit; pipeline YAML structure to the project's infra pack skills. Done when every baseline control has a current-state description, gap assessment, and remediation, with unsafe patterns cited by file.
Rules (never violate)
- Read-only audit: never install or configure scanners, or edit pipeline config, without team approval.
- Roadmap items (signing, provenance) are future work, never blockers.
- Only
@sha256:...is immutable —:v1.2.3and:mainare mutable tags; never confuse them. - A scanner without a blocking severity threshold is a gap — finding a scanner is not enough.
- CVE exemptions require a documented rationale and expiry date.
- Container CI/CD only — SSH device deploys and Terraform state are out of scope.
Resources
- Read
resources/gap-audit-procedure.mdwhen running the audit: the skill-boundary scope table, the 8-step procedure with checkpoints, the gap-report template and length budgets, self-check, mistakes, escalation, worked examples, and failure modes.
How to use
What it does
Audits your CI/CD pipeline's container image lifecycle against four baseline supply-chain controls plus two roadmap controls, returning a gap report that says, per control, what you have today, whether there is a gap, and what to change — every finding cited to file:line.
When to use it
- Does the pipeline block a build on a critical CVE, and where does the scan run?
- Deployments reference mutable tags like
:mainand you want@sha256:digests. - "Should we sign our images?" needs a readiness answer; a newly added scanner needs its threshold, ordering, and artifact storage checked.
What ships with it
1 file 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.
- 1mo ago First seen · 63 lines · 52 tokens per session scan A 4a5bb5e8257a
supply-chain-security is a skill published in the GitHub repository atretyak1985/swarmery (7 stars, last pushed 2d ago), licensed Apache-2.0. It adds 52 tokens to every session and 815 once invoked, about $0.0002 per session on Opus 5.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
azure-kubernetes-app-deploy
Use when deploying an existing web application or API to an already-running Azure Kubernetes Service cluster. Detects the framework, generates a Dockerfile and Kubernetes manifests, validates against AKS Deployment Safeguards, and deploys with verification. WHEN: deploy app to AKS, deploy to existing AKS cluster…
devops-deployment
Use when setting up CI/CD pipelines, containerizing applications, deploying to Kubernetes, or writing infrastructure as code. DevOps & Deployment covers GitHub Actions, Docker, Helm, and Terraform patterns.
aws-cloudformation-task-ecs-deploy-gh
Provides patterns to deploy ECS tasks and services with GitHub Actions CI/CD. Use when building Docker images, pushing to ECR, updating ECS task definitions, deploying ECS services, integrating with CloudFormation stacks, configuring AWS OIDC authentication for GitHub Actions, and implementing production-ready…
nextjs-deployment
Provides comprehensive patterns for deploying Next.js applications to production. Use when configuring Docker containers, setting up GitHub Actions CI/CD pipelines, managing environment variables, implementing preview deployments, or setting up monitoring and logging for Next.js applications. Covers standalone output…
devops
CI/CD, container orchestration, cloud architecture, monitoring, infrastructure security, and platform automation skills. Docker, Kubernetes, Terraform, GitHub Actions. Triggers on: CI/CD, Docker, Kubernetes, Terraform, deploy, monitoring, infra, GitOps, observability, SRE.
cloud-build-helper
Configures Google Cloud Build pipelines with caching, parallel builds, and optimization. Use when setting up Cloud Build, optimizing build performance, or configuring CI/CD pipelines.