Analyze GitHub Action Logs
withastro/astro
Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.
Audit GitHub Actions workflows with zizmor and explain reported hits using bundled trust-boundary references.
Install Zizmor
$ npx skills add alpha-omega-security/scrutineer --skill zizmor -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install alpha-omega-security/scrutineer zizmor --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/alpha-omega-security/scrutineer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/zizmor .claude/skills/zizmor && 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 "zizmor" agent skill from https://github.com/alpha-omega-security/scrutineer/tree/main/skills/zizmor into .claude/skills/zizmor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zizmor", 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/alpha-omega-security/scrutineer/tree/main/skills/zizmorType 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 alpha-omega-security/scrutineer --skill zizmor -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install alpha-omega-security/scrutineer zizmor --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alpha-omega-security/scrutineer.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/zizmor .agents/skills/zizmor && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "zizmor" agent skill from https://github.com/alpha-omega-security/scrutineer/tree/main/skills/zizmor into .agents/skills/zizmor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zizmor", 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 alpha-omega-security/scrutineer --skill zizmor -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install alpha-omega-security/scrutineer zizmor --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alpha-omega-security/scrutineer.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/zizmor .cursor/skills/zizmor && 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 "zizmor" agent skill from https://github.com/alpha-omega-security/scrutineer/tree/main/skills/zizmor into .cursor/skills/zizmor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zizmor", 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/alpha-omega-security/scrutineer.git --path skills/zizmor--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 alpha-omega-security/scrutineer --skill zizmor -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install alpha-omega-security/scrutineer zizmor --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alpha-omega-security/scrutineer.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/zizmor .gemini/skills/zizmor && 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 "zizmor" agent skill from https://github.com/alpha-omega-security/scrutineer/tree/main/skills/zizmor into .gemini/skills/zizmor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zizmor", 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 alpha-omega-security/scrutineer zizmorInstalls 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 alpha-omega-security/scrutineer --skill zizmor -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/alpha-omega-security/scrutineer.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/zizmor .github/skills/zizmor && 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 "zizmor" agent skill from https://github.com/alpha-omega-security/scrutineer/tree/main/skills/zizmor into .github/skills/zizmor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zizmor", 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 alpha-omega-security/scrutineer --skill zizmor -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install alpha-omega-security/scrutineer zizmor --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alpha-omega-security/scrutineer.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/zizmor .opencode/skills/zizmor && 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 "zizmor" agent skill from https://github.com/alpha-omega-security/scrutineer/tree/main/skills/zizmor into .opencode/skills/zizmor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zizmor", 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
zizmor- GitHub stars
- 239
- Token cost
- ~1.2k tokens
- SKILL.md length
- 519 words
- Files
- 12 (incl. scripts, references)
- Skills in repo
- 48
- Repo updated
- First seen
- Licence
- MIT
At a glance
Audit GitHub Actions workflows with zizmor and explain reported hits using bundled trust-boundary references.
- Works in 5 steps: Preserve its id, title, severity,… → Read every cited workflow location plus… → Load the relevant reference files listed… → …
- Tasks that involve CI/CD
- SKILL.md covers Workspace, Available scripts, References and What to do
- Runs Python scripts from its folder; calls python3
What it does
Zizmor is an agent skill from alpha-omega-security/scrutineer. Audit GitHub Actions workflows with zizmor and explain reported hits using bundled trust-boundary references.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including scripts and reference files (for example `references/comment-commands.md`, `references/examples.md` and `references/expression-injection.md`). Compatibility notes: Requires zizmor (https://github.com/zizmorcore/zizmor) and python3 on PATH. Reads bundled GitHub Actions security references from ./references; no external…
It sits in DevOps & Cloud, covering CI/CD. It works with GitHub Actions. The repository describes itself as: Security through scrutiny. The licence is MIT.
When your agent uses it
- Tasks that involve CI/CD
Example prompts
- “/zizmor”
Requirements
- Python 3
- Compatibility (from SKILL.md): Requires `zizmor` (https://github.com/zizmorcore/zizmor) and `python3` on PATH. Reads bundled GitHub Actions security references from `./references`; no external network access is needed.
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Preserve its id, title, severity, location, locations, and zizmor documentation reference exactly. Do not add, remove, merge, or…
- Read every cited workflow location plus enough surrounding YAML to identify the trigger, permissions, secrets, checkout ref, action…
- Load the relevant reference files listed above. Apply their false-positive controls as well as their attack patterns.
- Replace trace with a concise, source-grounded explanation of the complete chain: attacker-controlled input or mutable dependency, the…
- Replace rating with a concise justification for the preserved severity, tied to the actual token permissions, secrets, OIDC rights…
What it can do on your machine
Read from SKILL.md and the folder at commit f3407bf. 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
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3
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 no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires `zizmor` (https://github.com/zizmorcore/zizmor) and `python3` on PATH. Reads bundled GitHub Actions security references from `./references`; no external network access is needed.
From compatibility in the SKILL.md frontmatter.
Context cost
Zizmor loads about 1.2k tokens when it runs, and up to ~11k if it reads all its reference files. Until then it costs about 29 tokens; SKILL.md has 519 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); the scripts in this folder are not scanned.
SKILL.md
The full file from alpha-omega-security/scrutineer at commit f3407bf, republished under its MIT licence (© alpha-omega-security). 519 words, ~1,189 tokens.
Download SKILL.mdSave it as
.claude/skills/zizmor/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.- name
- zizmor
- description
- Audit GitHub Actions workflows with zizmor and explain reported hits using bundled trust-boundary references.
- compatibility
- Requires `zizmor` (https://github.com/zizmorcore/zizmor) and `python3` on PATH. Reads bundled GitHub Actions security references from `./references`; no external network access is needed.
- license
- MIT
- metadata.scrutineer.version
- 1
- metadata.scrutineer.output_file
- report.json
- metadata.scrutineer.output_kind
- findings
- metadata.scrutineer.model
- mid
zizmor
Run zizmor against ./src/.github/workflows, then explain each reported issue from the surrounding workflow and its effective trust boundary. The converter decides which findings exist; the reference pack helps make their exploit chain, impact, and remediation precise.
Workspace
./src— the cloned repository./scripts/scan.py— the wrapper./references— GitHub Actions attack-pattern and false-positive guidance./zizmor.json— intermediate findings emitted by the wrapper./report.json— write the findings report here./schema.json— output shape
Available scripts
scripts/scan.py— invokeszizmor --no-exit-codes --format json .github/workflowsand converts the output. If the repo has no workflows directory, it writes an empty result so the scan succeeds cleanly. zizmor's severity values are mapped to scrutineer's:unknown/informational/low→Low,medium→Medium,high→High,critical→Critical.
References
Read only the files relevant to each hit:
references/expression-injection.mdfor untrusted${{ }}expressions in shell, script, workflow-command, manual-input, and reusable-workflow contexts.references/privileged-pr-context.mdforpull_request_targetand other privileged jobs that materialize pull-request content.references/comment-commands.mdfor chatops authorization and approval-to-checkout TOCTOU.references/reusable-and-indirect-flows.mdforworkflow_call,workflow_run, local actions, artifacts, and caches crossing trust boundaries.references/permissions-secrets-runners.mdfor token scopes, secrets, OIDC, ArtiPACKED, caches, and self-hosted runners.references/supply-chain.mdfor mutable third-party action or reusable-workflow references and runtime downloads.references/examples.mdfor positive and negative examples that help distinguish an exploitable chain from hardening advice.
The references are review guidance, not evidence that the target is vulnerable. A finding's evidence must come from files under ./src and the locations emitted by zizmor.
What to do
python3 scripts/scan.py > ./zizmor.jsonThe script handles missing workflows directories, a missing zizmor binary, and zizmor's non-zero "I found something" exit code gracefully — don't add retry or error handling on top.
If zizmor.json contains an error or has no findings, copy it unchanged to report.json and stop.
For every finding in zizmor.json:
- Preserve its
id,title,severity,location,locations, and zizmor documentation reference exactly. Do not add, remove, merge, or reclassify findings. - Read every cited workflow location plus enough surrounding YAML to identify the trigger, permissions, secrets, checkout ref, action inputs, and commands involved. Follow repository-local reusable workflows, composite actions, and scripts only when the reported path depends on them.
- Load the relevant reference files listed above. Apply their false-positive controls as well as their attack patterns.
- Replace
tracewith a concise, source-grounded explanation of the complete chain: attacker-controlled input or mutable dependency, the interpreter or trust-boundary crossing, the privileges or secrets exposed, and the resulting operation. State any unresolved link instead of assuming it. - Replace
ratingwith a concise justification for the preserved severity, tied to the actual token permissions, secrets, OIDC rights, artifact visibility, runner trust, or write capability present in this repository. If impact depends on configuration outside the repository, say so explicitly.
Show full SKILL.md (81 more words)Show less
Do not turn generic hardening advice into a vulnerability. In particular, do not claim exploitation from broad permissions, a mutable action tag, pull_request_target, workflow_run, a self-hosted runner, or interpolation alone unless the checked-in workflow establishes the corresponding untrusted path and meaningful impact. Do not invent cloud trust policies, repository settings, secret values, or caller behavior that is not visible in ./src.
Write the enriched object to ./report.json and validate it against ./schema.json using the validation endpoint described in the system prompt.
© alpha-omega-security, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 11 other files (scripts, references) in skills/zizmor of alpha-omega-security/scrutineer.
- SKILL.md
- references/LICENSE.warden
- references/SOURCE
- references/comment-commands.md
- references/examples.md
- references/expression-injection.md
- references/permissions-secrets-runners.md
- references/privileged-pr-context.md
- references/reusable-and-indirect-flows.md
- references/supply-chain.md
- schema.json
- scripts/scan.py
Open the folder on GitHubat commit f3407bf
Compare with similar skills
Zizmor 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 |
|---|---|---|---|---|---|---|
| Zizmor this skillalpha-omega-security/scrutineer | 239 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Analyze GitHub Action Logswithastro/astro | 63k | 1 repos | ~1.3k | Automated safety check: Pass | Custom licence | |
| GitHub Actions Templatesbartstc/vite-ts-react-template | 122 | 14 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Nushellccusage/ccusage | 19k | — | ~938 | Automated safety check: Pass | Custom licence | |
| Repo Hygiene Scan and FixQwenLM/qwen-code | 28k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 260 | 6 repos | ~1.1k | Automated safety check: Notes | Custom licence |
Similar skills
- Official
GitHub Actions Templates
bartstc/vite-ts-react-template
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications.
Nushell
ccusage/ccusage
Guides ccusage Nushell scripts. An agent skill from ccusage/ccusage.
Repo Hygiene Scan and Fix
QwenLM/qwen-code
Scheduled CI skill that scans a repository for small, certain docs, test and code hygiene issues and fixes them on one branch with a commit per finding.
Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
CI Failure Triage and Repair
Chachamaru127/claude-code-harness
Diagnoses failing CI pipelines and tests, deciding first whether the test or the implementation is at fault, and hands hard cases to a dedicated fixer subagent.
More from alpha-omega-security/scrutineer
All 48 skills in this repoTriage
alpha-omega-security/scrutineer
Default pipeline scrutineer runs when a repository is added.
Bandit
alpha-omega-security/scrutineer
Run bandit against the Python source in the repository and map its hits into the findings shape.
Compliance
alpha-omega-security/scrutineer
Audit the repository against the OpenSSF Baseline with darnit, resolve the controls darnit defers to LLM analysis or could not verify, and record per-control verdicts plus the attained Baseline level.
Dependencies
alpha-omega-security/scrutineer
Run git-pkgs list and sbom against the repository and emit one envelope with per-section status.
History
alpha-omega-security/scrutineer
Mine repository history for security fixes that were never published as advisories, producing a cached worklist for threat-model and advisory-deep-dive.
Maintainers
alpha-omega-security/scrutineer
Identify the real maintainers of a repository and the best way to contact them about a security issue.
Related
Works with
Categories
Questions about Zizmor
What does Zizmor do?
Audit GitHub Actions workflows with zizmor and explain reported hits using bundled trust-boundary references. Zizmor is an agent skill from alpha-omega-security/scrutineer. Audit GitHub Actions workflows with zizmor and explain reported hits using bundled trust-boundary references.
When should I use Zizmor?
Zizmor fits situations like: tasks that involve CI/CD.
How do I install Zizmor in Claude Code?
Run `npx skills add alpha-omega-security/scrutineer --skill zizmor -a claude-code`. Or copy the skill folder (skills/zizmor in alpha-omega-security/scrutineer) into .claude/skills/zizmor in your project. Claude Code loads it when a task matches its description.
How do I install Zizmor in Codex?
Run `npx skills add alpha-omega-security/scrutineer --skill zizmor -a codex`. Or copy the skill folder (skills/zizmor in alpha-omega-security/scrutineer) into .agents/skills/zizmor in your project. Codex loads it when a task matches its description.
Can I use Zizmor 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 alpha-omega-security/scrutineer --skill zizmor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/zizmor, .gemini/skills/zizmor, .github/skills/zizmor and .opencode/skills/zizmor in your project.
What does Zizmor need to run?
Going by SKILL.md and its folder, Zizmor needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3. Compatibility (from SKILL.md): Requires `zizmor` (https://github.com/zizmorcore/zizmor) and `python3` on PATH. Reads bundled GitHub Actions security references from `./references`; no external network access is needed..
Does Zizmor 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 Zizmor 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Zizmor use?
Zizmor is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Zizmor use?
About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 9.8k tokens, read only when the agent opens those files.
What are the alternatives to Zizmor?
Skills that share tags, products or a category with Zizmor: Analyze GitHub Action Logs (withastro/astro, 63k stars), GitHub Actions Templates (bartstc/vite-ts-react-template, 122 stars), Nushell (ccusage/ccusage, 19k stars) and Repo Hygiene Scan and Fix (QwenLM/qwen-code, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Zizmor?
alpha-omega-security (a GitHub organization) maintains it in alpha-omega-security/scrutineer, which has 239 GitHub stars. The repository holds 48 skills in this directory. The repository was last updated on October 9, 2026.
Source: alpha-omega-security/scrutineer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.