Skip to content

[Skill] Github security audit#2098

Open
arielkr256 wants to merge 1 commit into
developfrom
github-sec-audit-skill
Open

[Skill] Github security audit#2098
arielkr256 wants to merge 1 commit into
developfrom
github-sec-audit-skill

Conversation

@arielkr256

Copy link
Copy Markdown
Contributor

Use when the user asks to audit GitHub Actions workflows for security vulnerabilities, supply chain risks, script injection, dangerous triggers, or attack vectors from the Wiz GitHub Actions threat model. Triggers on requests like "check my GitHub Actions for vulnerabilities", "audit workflows for pwn requests", "scan for script injection in workflows", "check if actions are pinned to commit SHAs", or "audit all public repos for GitHub Actions issues".

@arielkr256 arielkr256 requested review from a team as code owners June 12, 2026 18:00
@cursor

cursor Bot commented Jun 12, 2026

Copy link
Copy Markdown

PR Summary

Low Risk
Adds documentation-style skill configuration only; no runtime, auth, or workflow execution changes in this repo.

Overview
Adds a new Panther AI skill github_actions_security_audit_skill that guides automated audits of GitHub Actions workflows against the Wiz threat model.

The skill prompt walks through optional org-wide repo discovery via git_hub_search_repositories, workflow discovery with git_hub_get_file_contents / git_hub_search_code, and checks for dangerous triggers (e.g. pwn-request patterns with pull_request_target), script injection in run: blocks, and unpinned third-party actions. It ends with a structured report template (summary table, detailed findings, remediation, overall risk posture).

Metadata wires RequiredTools to the three GitHub MCP tools above, plus tags for github, supply-chain, ci-cd, and security-audit.

Reviewed by Cursor Bugbot for commit 32036ab. Bugbot is set up for automated code reviews on this repo. Configure here.

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes using default effort and found 3 potential issues.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 32036ab. Configure here.


If the user has **not** specified a particular `owner/repo`, use **`git_hub_search_repositories`** to enumerate all public repositories for the target organization or user before auditing.

1. Call `git_hub_search_repositories` with a query such as `org:<org-name> is:public` (or `user:<username> is:public`) to list all public repositories.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Step zero lacks org identity

Medium Severity

Step 0 requires org:&lt;org-name&gt; or user:&lt;username&gt; in git_hub_search_repositories but never says how to obtain that target when the user did not name a repository or organization, so discovery can stall or guess wrong.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 32036ab. Configure here.


1. Call `git_hub_search_repositories` with a query such as `org:<org-name> is:public` (or `user:<username> is:public`) to list all public repositories.
2. Collect the full list of `owner/repo` identifiers from the results.
3. For each repository discovered, proceed with Steps 1–4 below to audit its `.github/workflows/` directory.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Multi-repo report timing unclear

Medium Severity

Step 0 loops Steps 1–4 per discovered repo but never states that Step 5 runs once after all repos. Step 5’s “Total repositories scanned” implies one combined report, so agents may emit partial reports or wrong totals.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 32036ab. Configure here.


Alternatively, use **`git_hub_search_code`** to locate workflow files across a repository or organization:
- Query example: `path:.github/workflows extension:yml` scoped to the target repo.
- This is useful when the repository structure is unknown or when scanning multiple repositories.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Search tip omits yaml extension

Low Severity

Step 1’s git_hub_search_code example uses extension:yml only, while Step 1 also expects .yaml workflow files, so code search may miss workflows that use the .yaml suffix.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 32036ab. Configure here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ai Skills, prompts, and tools for Panther AI and local coding agents.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant