What is ci-cd-supply-chain-security?

A security review guide for continuous integration and delivery (CI/CD) pipelines and software supply chains. CI/CD automates building and releasing software, while a software supply chain includes its dependencies, tools, and build artifacts.

Use it to audit GitHub Actions, GitLab CI, Jenkins, CircleCI, container builds, package registries, deployment targets, and related pipeline configuration.

It helps identify ways attackers could expose secrets, poison dependencies, alter build outputs, or compromise the environment that ships software.

ci-cd-supply-chain-security — Skill by Samurai-goose

Install

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.

Any agent

npx skills add Samurai-goose/SPECTER-The-Illusive-Security-Protocol --skill ci-cd-supply-chain-security

Clone the repo

git clone --depth 1 https://github.com/Samurai-goose/SPECTER-The-Illusive-Security-Protocol

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/samurai-goose/specter-the-illusive-security-protocol/ci-cd-supply-chain-security/github.svg)](https://agentmods.dev/skills/samurai-goose/specter-the-illusive-security-protocol/ci-cd-supply-chain-security)

Your own site

<a href="https://agentmods.dev/skills/samurai-goose/specter-the-illusive-security-protocol/ci-cd-supply-chain-security"><img src="https://agentmods.dev/badge/skills/samurai-goose/specter-the-illusive-security-protocol/ci-cd-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/samurai-goose/specter-the-illusive-security-protocol/ci-cd-supply-chain-security"><img src="https://agentmods.dev/badge/skills/samurai-goose/specter-the-illusive-security-protocol/ci-cd-supply-chain-security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,942 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00051	$0.01942
Opus 5.5	$0.00020	$0.00777
Sonnet 5.5	$0.00010	$0.00388
Haiku 4.5	$0.00005	$0.00194

Measured 2mo ago against content hash 2495b7ec299a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ci-cd-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 2mo 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.

ci-cd-supply-chain-security/SKILL.md · 208 lines

How it starts

The opening of the file, as written. The whole thing — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CI/CD & Supply Chain Security

Purpose

Audit continuous integration/delivery pipelines and software supply chains for compromise vectors. CI/CD systems are high-value targets: they hold deployment credentials, build artifacts, and have write access to production. Supply chain attacks (dependency confusion, typosquatting, artifact tampering) bypass traditional application security controls entirely.

Triggers

CI/CD configuration files found in repository (.github/workflows, .gitlab-ci.yml, Jenkinsfile)
User requests pipeline security review
Dependency audit surfaces supply chain concerns
New deployment pipeline being configured
Security governance engagement includes infrastructure

Required Inputs

Input	Description	Required
`governance_context`	Active engagement governance record	Yes
`pipeline_configs`	CI/CD config files (workflow YAML, Jenkinsfile, etc.)	Yes
`ci_platform`	GitHub Actions, GitLab CI, Jenkins, CircleCI, etc.	Auto-detected
`package_registries`	npm, PyPI, Docker Hub, internal registries in use	Recommended
`deployment_targets`	Where artifacts deploy to (cloud, K8s, servers)	Recommended

Workflow

Scope Verification — Confirm CI/CD systems and registries are within authorized scope.
Pipeline Configuration Review

GitHub Actions:
- Review all workflow files in .github/workflows/
- Check pull_request_target trigger (runs with write access on untrusted PR)
- Check workflow_run chaining for privilege escalation
- Review permissions: block — avoid default write-all
- Check for ${{ github.event.*.body }} or similar injection in run: steps
- Verify actions pinned to SHA (not tag/branch — mutable references)
- Review third-party actions for trust (verified publisher, source audit)
- Check GITHUB_TOKEN permissions scope
- Review secret access: which jobs/steps can access which secrets?
- Check for if: conditions that can be bypassed
- Review artifact upload/download for path traversal

Read the full file on GitHub · 208 lines

Changes

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.

2mo ago First seen · 208 lines · 51 tokens per session scan A 2495b7ec299a

Subscribe to this mod's changes

ci-cd-supply-chain-security is a skill published in the GitHub repository Samurai-goose/SPECTER-The-Illusive-Security-Protocol (3 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 1,942 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-08-31.

CI and CD DevOps and cloud Security

ci-cd-supply-chain-security next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
ci-cd-supply-chain-securitySamurai-goose/SPECTER-The-Illusive-Security-Protocol	Skill	3	4mo ago	MIT	A	51	Claude Code, Codex
chinese-git-workflowjnMetaCode/superpowers-zh	Skill	8.5k	12d ago	MIT	A	69	Claude Code
atmos-profilescloudposse/atmos	Skill	1.4k	today	Apache-2.0	A	35	Claude Code
webhook-managementhoangsonww/Claude-Code-Agent-Monitor	Skill	1.2k	yesterday	MIT	A	56	Claude Code, Codex
monorepo-managementwshobson/agents	Skill	42k	2d ago	MIT	C	54	Claude Code
managing-github-actions-secretsPostHog/posthog-foss	Skill	728	today	MIT	A	67	Claude Code, Codex
postman-newman-automationLambdaTest/agent-skills	Skill	391	2d ago	MIT	A	156	Claude Code, Codex