Skip to content

Add security-tools plugin (secure-github-actions)#4

Merged
MrDHat merged 5 commits into
mainfrom
akshay/open-source-security-tools
Jul 9, 2026
Merged

Add security-tools plugin (secure-github-actions)#4
MrDHat merged 5 commits into
mainfrom
akshay/open-source-security-tools

Conversation

@MrDHat

@MrDHat MrDHat commented Jul 9, 2026

Copy link
Copy Markdown
Member

Why?

Continuing the effort to open-source broadly-useful, well-adopted Claude Code skills. secure-github-actions is a general-purpose GitHub Actions hardening reviewer with no organization-specific coupling — valuable to anyone running Actions.

How?

Adds the security-tools plugin to the fin-2x marketplace:

  • secure-github-actions — harden GitHub Actions workflows against supply-chain and injection attacks. A 14-rule review checklist (expression injection, SHA-pinning, least-privilege permissions:, pull_request_target, OIDC, and public-repo rules) plus a set of audit grep commands.
  • auto-inject hook — a non-blocking PostToolUse hook that reminds Claude to load the skill whenever a .github/workflows/*.yml file is read or edited, so workflow changes get the hardening review automatically.

Ported from an internal Claude Code plugin collection; organization-specific action allowlists, incident references, and internal reusable-workflow examples were genericized. The original author is credited via Co-Authored-By trailers. Commit structure: one bootstrap commit, one for the skill, one for the hook, one marketplace-registration commit.

Generated with Claude Code

MrDHat and others added 4 commits July 9, 2026 12:57
Scaffold the security-tools plugin — keep CC-authored CI and code safe.
Manifest, README, CHANGELOG, and MIT license. Skills added in follow-up commits.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Harden GitHub Actions workflows against supply-chain and injection attacks — a
14-rule review checklist plus audit commands. Ported from an internal Claude
Code plugin collection; organization-specific action allowlists, incident
references, and internal reusable-workflow examples were genericized.

Co-Authored-By: Jacopo Scrinzi <10990391+eredi93@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…dits

Add a PostToolUse hook that fires when a file under .github/workflows/ (or
.github/workflows-disabled/) is read or edited and reminds Claude to load the
secure-github-actions skill, so workflow changes get the hardening review
automatically. Non-blocking — it only injects a context reminder. Ported from
an internal Claude Code plugin collection and genericized.

Co-Authored-By: Jacopo Scrinzi <10990391+eredi93@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Add security-tools to the marketplace manifest and root README.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Comment thread plugins/security-tools/skills/secure-github-actions/SKILL.md Outdated
Comment thread plugins/security-tools/skills/secure-github-actions/SKILL.md
Comment thread plugins/security-tools/skills/secure-github-actions/SKILL.md Outdated
Comment thread plugins/security-tools/skills/secure-github-actions/SKILL.md
…and CI-agnostic

Generalize the description and When-NOT-to-Use exclusions so they don't read as
JS/Ruby-specific. Claude could otherwise latch onto npm/pnpm/Gemfile/Buildkite/
CircleCI names and skip the skill on a Java/Go/Python codebase that still has a
workflow YAML to harden.

Also drop Rule 3's trusted-reusable-workflow exception and reconcile downstream:
remove the contradicting checklist line and SHA-pin the reusable-workflow examples.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@MrDHat
MrDHat force-pushed the akshay/open-source-security-tools branch from ef6016e to ed2e5ff Compare July 9, 2026 13:41
@MrDHat
MrDHat requested a review from normprovost July 9, 2026 13:42
@MrDHat
MrDHat merged commit 550921f into main Jul 9, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants