agentic-actions-auditor

Audit GitHub Actions workflows for AI agent security vulnerabilities.

Updated Jul 4, 2026
One-click install
npx skills add https://github.com/kimen-dev/kimen --skill agentic-actions-auditor-kimen-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentic-actions-auditor
Source: https://github.com/kimen-dev/kimen/tree/main/.agents/skills/agentic-actions-auditor
Command: npx skills add https://github.com/kimen-dev/kimen --skill agentic-actions-auditor-kimen-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies critical security vulnerabilities in GitHub Actions workflows that integrate AI coding agents, preventing unauthorized access and prompt injection risks.

Core Features & Use Cases

  • Static Security Analysis: Detects dangerous patterns like env var intermediary injection, direct expression injection, and subshell expansion bypasses.
  • Cross-File Resolution: Automatically traces AI agent usage through composite actions and reusable workflows to uncover hidden risks.
  • Use Case: Before merging a new CI/CD workflow that uses an AI coding agent, run this audit to ensure that attacker-controlled input from PRs or issues cannot reach the AI prompt or trigger unauthorized shell commands.

Quick Start

Use the agentic-actions-auditor skill to audit the GitHub Actions workflows in the current repository for AI agent security vulnerabilities.

Frequently Asked Questions about agentic-actions-auditor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit GitHub Actions workflows for AI agent prompt injection risks?

To audit GitHub Actions workflows for AI agent prompt injection risks, use static analysis to trace attacker-controlled input from PRs or issues to AI prompts and detect dangerous env var intermediary patterns and subshell expansion bypasses in your CI/CD pipeline configuration.

What is an env var intermediary pattern in CI/CD security?

An env var intermediary pattern in CI/CD security is an attack vector where attacker-controlled input is passed through environment variables to AI agents, creating prompt injection risks that allow unauthorized shell command execution or malicious prompt manipulation in GitHub Actions workflows.

How do I detect dangerous sandbox configurations in GitHub Actions?

Detect dangerous sandbox configurations in GitHub Actions by performing static security analysis on workflow files to identify overly permissive tool allowlists and trace AI agent usage through composite actions and reusable workflows for hidden security vulnerabilities.

Can static analysis trace AI agent usage through composite actions and reusable workflows?

Yes, static analysis can automatically trace AI agent usage through composite actions and reusable workflows via cross-file resolution to uncover hidden security vulnerabilities and direct expression injection risks in your CI/CD pipeline configurations.

When do I need to run a security audit on CI/CD pipelines using AI coding agents?

Run a security audit on CI/CD pipelines using AI coding agents before merging new workflows to ensure attacker-controlled input from PRs or issues cannot reach the AI prompt or trigger unauthorized shell commands through dangerous sandbox configurations.

What are the limitations of static analysis for detecting prompt injection in GitHub Actions?

Static analysis for detecting prompt injection in GitHub Actions is limited to identifying known dangerous patterns in workflow files, env var intermediaries, and subshell expansion bypasses, and may not catch dynamically generated code or runtime-only prompt injection vectors.