GitHub Actions Supply Chain Pinning
asyncapi/generator
A skill your agent uses when editing, adding, or reviewing any file under .github/workflows/, or when a CI step installs a CLI tool (npm i -g, npx, pipx, uses: /setup-).
CI/CD pipeline security, supply chain security, SLSA compliance, artifact signing, dependency scanning
Install CI CD Security
$ npx skills add Hack23/cia --skill ci-cd-security -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Hack23/cia ci-cd-security --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/ci-cd-security .claude/skills/ci-cd-security && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ci-cd-security" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/ci-cd-security into .claude/skills/ci-cd-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-cd-security", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Hack23/cia/tree/master/.github/skills/ci-cd-securityType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Hack23/cia --skill ci-cd-security -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Hack23/cia ci-cd-security --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/ci-cd-security .agents/skills/ci-cd-security && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ci-cd-security" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/ci-cd-security into .agents/skills/ci-cd-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-cd-security", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Hack23/cia --skill ci-cd-security -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Hack23/cia ci-cd-security --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/ci-cd-security .cursor/skills/ci-cd-security && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ci-cd-security" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/ci-cd-security into .cursor/skills/ci-cd-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-cd-security", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Hack23/cia.git --path .github/skills/ci-cd-security--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Hack23/cia --skill ci-cd-security -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Hack23/cia ci-cd-security --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/ci-cd-security .gemini/skills/ci-cd-security && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ci-cd-security" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/ci-cd-security into .gemini/skills/ci-cd-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-cd-security", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Hack23/cia ci-cd-securityInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Hack23/cia --skill ci-cd-security -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/ci-cd-security .github/skills/ci-cd-security && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ci-cd-security" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/ci-cd-security into .github/skills/ci-cd-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-cd-security", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Hack23/cia --skill ci-cd-security -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Hack23/cia ci-cd-security --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/ci-cd-security .opencode/skills/ci-cd-security && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ci-cd-security" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/ci-cd-security into .opencode/skills/ci-cd-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-cd-security", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ci-cd-security- GitHub stars
- 239
- Token cost
- ~1.3k tokens
- SKILL.md length
- 330 words
- Files
- 1
- Skills in repo
- 78
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
CI/CD pipeline security, supply chain security, SLSA compliance, artifact signing, dependency scanning
- Works in 5 steps: Pin all action versions to commit SHAs —… → Use permissions at job level — minimize… → Never echo secrets — use ::add-mask::… → …
- Tasks that involve Supply chain security
- SKILL.md covers Purpose, When to Use, GitHub Actions Security… and Supply Chain Security, plus 5 more sections
- Calls mvn; needs SONAR_TOKEN
What it does
CI CD Security is an agent skill from Hack23/cia. CI/CD pipeline security, supply chain security, SLSA compliance, artifact signing, dependency scanning
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Security, covering Supply chain security and CI/CD. It works with GitHub Actions. The repository describes itself as: Citizen Intelligence Agency. Open-source intelligence platform analyzing Swedish political activities using AI and data visualization. Tracks politicians, government… The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Supply chain security
- Tasks that involve CI/CD
Example prompts
- “/ci-cd-security”
Requirements
- A credential in SONAR_TOKEN
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Pin all action versions to commit SHAs — tags can be moved
- Use permissions at job level — minimize token scope
- Never echo secrets — use ::add-mask:: for dynamic values
- Audit third-party actions — review source before adopting
- Use CODEOWNERS for workflow files — require review for changes
What it can do on your machine
Read from SKILL.md and the folder at commit 6a9797b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
mvn
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
SONAR_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
CI CD Security loads about 1.3k tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 330 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Hack23/cia at commit 6a9797b, republished under its Apache-2.0 licence (© Hack23). 330 words, ~1,327 tokens.
Download SKILL.mdSave it as
.claude/skills/ci-cd-security/SKILL.md (or your agent's skills folder).- name
- ci-cd-security
- description
- CI/CD pipeline security, supply chain security, SLSA compliance, artifact signing, dependency scanning
- license
- Apache-2.0
CI/CD Security Skill
Purpose
Secure the CIA platform's CI/CD pipelines against supply chain attacks, ensure artifact integrity, and maintain compliance with SLSA (Supply-chain Levels for Software Artifacts) requirements. Covers GitHub Actions hardening, dependency scanning, and build provenance.
When to Use
- ✅ Creating or modifying GitHub Actions workflows
- ✅ Adding new dependencies to the project
- ✅ Configuring build artifact signing or attestation
- ✅ Reviewing pipeline security posture
- ✅ Implementing dependency update policies
Do NOT use for:
- ❌ Application-level security (use secure-code-review skill)
- ❌ Infrastructure security (use threat-modeling skill)
GitHub Actions Security Hardening
Workflow Permissions
# Always use minimum required permissions
permissions:
contents: read
actions: read
security-events: write # Only if needed for CodeQL
# Pin actions to full SHA, not tags
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
- uses: actions/setup-java@99b8673ff64fbf99d8d325f52d9a5bdedb8483e9 # v4.2.1
with:
distribution: 'temurin'
java-version: '25'Key Security Rules
- Pin all action versions to commit SHAs — tags can be moved
- Use
permissionsat job level — minimize token scope - Never echo secrets — use
::add-mask::for dynamic values - Audit third-party actions — review source before adopting
- Use
CODEOWNERSfor workflow files — require review for changes
Secret Management
# Good: Use GitHub Secrets
env:
SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
# Bad: Never hardcode or log secrets
# run: echo ${{ secrets.TOKEN }} # NEVER DO THISSupply Chain Security
SLSA Compliance Levels
| Level | Requirement | CIA Status |
|---|---|---|
| SLSA 1 | Build process documented | ✅ GitHub Actions |
| SLSA 2 | Hosted build, signed provenance | ✅ GitHub-hosted runners |
| SLSA 3 | Hardened build, non-falsifiable provenance | 🔄 In progress |
Dependency Scanning Stack
# Multi-layer dependency scanning
- name: OWASP Dependency Check
run: mvn dependency-check:check -DfailBuildOnCVSS=7
- name: GitHub Dependency Review
uses: actions/dependency-review-action@v4
with:
fail-on-severity: high
- name: Dependabot Auto-merge (patch only)
# Configured in .github/dependabot.ymlSBOM Generation
- name: Generate SBOM
run: |
mvn org.cyclonedx:cyclonedx-maven-plugin:makeBom
# Output: target/bom.json (CycloneDX format)
- name: Attest SBOM
uses: actions/attest-sbom@v1
with:
subject-path: 'target/*.jar'
sbom-path: 'target/bom.json'Build Integrity
Reproducible Builds
<!-- Maven settings for reproducible builds -->
<properties>
<project.build.outputTimestamp>2024-01-01T00:00:00Z</project.build.outputTimestamp>
</properties>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<archive>
<manifest>
<addDefaultImplementationEntries>true</addDefaultImplementationEntries>
</manifest>
</archive>
</configuration>
</plugin>Artifact Attestation
- name: Generate artifact attestation
uses: actions/attest-build-provenance@v1
with:
subject-path: 'target/citizen-intelligence-agency-*.war'Dependency Management Rules
Adding New Dependencies
- Check license compatibility — must be Apache 2.0 compatible
- Run security scan —
mvn dependency-check:check - Check GitHub Advisory Database — use
gh-advisory-databasetool - Verify publisher — check Maven Central publisher identity
- Pin version — use exact versions, not ranges
- Document justification — explain why the dependency is needed in PR
Dependency Update Policy
| Update Type | Auto-merge | Review Required |
|---|---|---|
| Patch (x.x.PATCH) | ✅ If tests pass | No |
| Minor (x.MINOR.x) | ❌ | Yes |
| Major (MAJOR.x.x) | ❌ | Yes + security review |
Runner Security
jobs:
build:
runs-on: ubuntu-latest # Use GitHub-hosted runners
# Never use self-hosted runners for public repos without hardening
steps:
- name: Harden Runner
uses: step-security/harden-runner@v2
with:
egress-policy: audit # Monitor outbound connectionsMonitoring and Alerts
- Enable Dependabot alerts for all ecosystems
- Enable secret scanning with push protection
- Enable code scanning with CodeQL
- Review Security tab weekly for new alerts
- Monitor OSSF Scorecard results for security posture
ISMS Alignment
| Control | Requirement |
|---|---|
| ISO 27001 A.8.25 | Secure development lifecycle |
| ISO 27001 A.8.31 | Separation of dev/test/prod |
| NIST CSF PR.IP-1 | Configuration management |
| CIS Control 16 | Application software security |
| SLSA L2 | Signed provenance, hosted build |
© Hack23, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .github/skills/ci-cd-security of Hack23/cia.
Open the folder on GitHubat commit 6a9797b
Compare with similar skills
CI CD Security next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| CI CD Security this skillHack23/cia | 239 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| GitHub Actions Supply Chain Pinningasyncapi/generator | 1.1k | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Vibe CI Supply Chainmistralai/mistral-vibe | 5.1k | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| CI/CD Pipeline Principlesirahardianto/awesome-agv | 157 | — | ~2.7k | Automated safety check: Notes | MIT | |
| Atmos CIcloudposse/atmos | 1.4k | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| Detecting Supply Chain Attacks In CI CDmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~655 | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Vibe CI Supply Chain
mistralai/mistral-vibe
Git workflow, CI/GitHub Actions, and supply-chain pinning rules for Mistral Vibe.
CI/CD Pipeline Principles
irahardianto/awesome-agv
Rules for designing CI/CD pipelines in layers: universal lint, test and scan stages, container builds with SBOM attestation, and GitOps for orchestrated deployments.
Atmos CI
cloudposse/atmos
Atmos CI: Native CI with GitHub Actions containers, native outputs, SBOM workflow-artifact publication, collapsible log groups, affected/all matrix workflows, OIDC profiles, toolchain-aware jobs…
Detecting Supply Chain Attacks In CI CD
mukul975/Anthropic-Cybersecurity-Skills
Scans GitHub Actions workflows and CI/CD pipeline configurations for supply chain attack vectors including unpinned actions, script injection via expressions, dependency confusion, and secrets…
Supply Chain Guard
davila7/claude-code-templates
Detect and remediate software supply chain attacks in npm, PyPI, crates.io, GitHub Actions, and CI/CD pipelines by scanning for known compromised packages, malicious versions, filesystem IOCs, C2…
More from Hack23/cia
All 78 skills in this repoAccessibility Wcag Patterns
Hack23/cia
WCAG 2.1 AA compliance, ARIA attributes, keyboard navigation, screen reader optimization for accessible political data platforms
Advanced Data Visualization
Hack23/cia
Advanced chart types, D3.js/Vaadin Charts patterns, political data visualization, time series analysis
AI Governance
Hack23/cia
AI governance, EU AI Act compliance, OWASP LLM security, responsible AI practices for GitHub Copilot agents
API Integration
Hack23/cia
External API integration patterns, retry logic, circuit breakers, caching, rate limiting for government data APIs
AWS Cloudwatch Monitoring
Hack23/cia
AWS CloudWatch metrics, alarms, dashboards, log insights, and application monitoring for the CIA platform
AWS Security Architecture
Hack23/cia
AWS security best practices, VPC security, IAM, KMS, CloudTrail, GuardDuty for CIA platform deployment
Related
Works with
Categories
Questions about CI CD Security
What does CI CD Security do?
CI/CD pipeline security, supply chain security, SLSA compliance, artifact signing, dependency scanning. CI CD Security is an agent skill from Hack23/cia.
When should I use CI CD Security?
CI CD Security fits situations like: tasks that involve Supply chain security; tasks that involve CI/CD.
How do I install CI CD Security in Claude Code?
Run `npx skills add Hack23/cia --skill ci-cd-security -a claude-code`. Or copy the skill folder (.github/skills/ci-cd-security in Hack23/cia) into .claude/skills/ci-cd-security in your project. Claude Code loads it when a task matches its description.
How do I install CI CD Security in Codex?
Run `npx skills add Hack23/cia --skill ci-cd-security -a codex`. Or copy the skill folder (.github/skills/ci-cd-security in Hack23/cia) into .agents/skills/ci-cd-security in your project. Codex loads it when a task matches its description.
Can I use CI CD Security in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Hack23/cia --skill ci-cd-security -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ci-cd-security, .gemini/skills/ci-cd-security, .github/skills/ci-cd-security and .opencode/skills/ci-cd-security in your project.
What does CI CD Security need to run?
Going by SKILL.md and its folder, CI CD Security needs the command-line tools its instructions call (mvn) and credentials named SONAR_TOKEN. Our summary lists: A credential in SONAR_TOKEN.
Does CI CD Security access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is CI CD Security safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does CI CD Security use?
CI CD Security is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does CI CD Security use?
About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to CI CD Security?
Skills that share tags, products or a category with CI CD Security: GitHub Actions Supply Chain Pinning (asyncapi/generator, 1.1k stars), Vibe CI Supply Chain (mistralai/mistral-vibe, 5.1k stars), CI/CD Pipeline Principles (irahardianto/awesome-agv, 157 stars) and Atmos CI (cloudposse/atmos, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains CI CD Security?
Hack23 (a GitHub organization) maintains it in Hack23/cia, which has 239 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 6, 2026.
Source: Hack23/cia on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.