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 iamBrzDev/enterprise-agent-skills --skill secure-supply-chaingit clone --depth 1 https://github.com/iamBrzDev/enterprise-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/iambrzdev/enterprise-agent-skills/secure-supply-chain)<a href="https://agentmods.dev/skills/iambrzdev/enterprise-agent-skills/secure-supply-chain"><img src="https://agentmods.dev/badge/skills/iambrzdev/enterprise-agent-skills/secure-supply-chain/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/iambrzdev/enterprise-agent-skills/secure-supply-chain"><img src="https://agentmods.dev/badge/skills/iambrzdev/enterprise-agent-skills/secure-supply-chain.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.00148 | $0.02709 |
| Opus 5.5 | $0.00059 | $0.01084 |
| Sonnet 5.5 | $0.00030 | $0.00542 |
| Haiku 4.5 | $0.00015 | $0.00271 |
Grade A, and why
secure-supply-chain 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 — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to activate
- "We need an SBOM" — for a customer, an audit, or a procurement questionnaire
- Adding or reviewing dependency scanning in a pipeline
- A CVE lands in a transitive dependency and nobody can say where it is used
- Pinning GitHub Actions, container base images, or package versions
- Signing artifacts or container images, or verifying them before deploy
- A compliance requirement names SLSA, NIST SP 800-218 (SSDF), or the EU CRA
- Reviewing a pipeline that installs dependencies without a lockfile
Rules — Non-negotiable
-
The lockfile is committed and CI installs from it.
composer installwithoutcomposer.lock, ordotnet restoreagainst floating versions, resolves different code than the developer tested. Use--locked,--frozen-lockfile, or a committedpackages.lock.json. -
Pin third-party GitHub Actions by commit SHA, not by tag. A tag is mutable: whoever controls the repository can repoint
v4at new code, and your pipeline runs it with your secrets on the next execution. -
Pin container base images by digest, not by tag. A tag moves. A
@sha256:digest does not. -
Generate the SBOM from the build, not from the source afterwards. An SBOM produced by scanning a repository lists what the manifest declares. An SBOM produced from the build output lists what actually shipped.
-
Verify signatures at deploy, not only produce them at build. A signature nobody checks is a log line, not a control.
-
No signing keys in the repository, in CI variables, or in a vault you manage. Use keyless signing bound to the workflow's OIDC identity.
-
Gate on exploitability, not on raw CVE count. A build that fails on every medium CVE gets bypassed within a month. Fail on critical with a fix available; report the rest.
The four control points
Source → Build → Artifact → Deploy
│ │ │ │
│ │ │ └─ verify signature + provenance before running
│ │ └─ sign, attest, publish the SBOM beside the artifact
│ └─ pinned, from a lockfile; generate the SBOM here
└─ lockfile committed, dependency review on every PR
What ships with it
3 files 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 · 320 lines · 148 tokens per session scan A 795e984a38f7
secure-supply-chain is a skill published in the GitHub repository iamBrzDev/enterprise-agent-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 148 tokens to every session and 2,709 once invoked, about $0.0006 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-09.
Other skills, from other repositories
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
devops
DevOps - Docker, CI/CD, cloud infra, monitoring.
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.
performing-container-security-scanning-with-trivy
Scan container images, filesystems, and Kubernetes manifests for vulnerabilities, misconfigurations, exposed secrets, and license compliance issues using Aqua Security Trivy with SBOM generation and CI/CD integration.
devops-infrastructure
Guides Docker, CI/CD pipelines, deployment strategies, infrastructure as code, and observability setup. Use when writing Dockerfiles, configuring GitHub Actions, planning deployments, setting up monitoring, or when asked about containers, pipelines, Terraform, or production infrastructure.
CI/CD Pipeline Advanced
Expert-level CI/CD pipeline skill for test automation. Covers GitHub Actions, Jenkins, GitLab CI, Azure DevOps, parallel execution, matrix strategies, caching, artifact management, and deployment gates.