Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add nitinjain999/platform-skills --skill zizmorgit clone --depth 1 https://github.com/nitinjain999/platform-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/nitinjain999/platform-skills/zizmor)<a href="https://agentmods.dev/skills/nitinjain999/platform-skills/zizmor"><img src="https://agentmods.dev/badge/skills/nitinjain999/platform-skills/zizmor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/nitinjain999/platform-skills/zizmor"><img src="https://agentmods.dev/badge/skills/nitinjain999/platform-skills/zizmor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00175 | $0.06274 |
| Opus 5.5 | $0.00070 | $0.02510 |
| Sonnet 5.5 | $0.00035 | $0.01255 |
| Haiku 4.5 | $0.00017 | $0.00627 |
Grade A, and why
zizmor scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit GitHub Actions workflows for security findings — before an attacker reads them for you.
Read references/zizmor.md before responding. It contains bootstrap steps, the full 41-audit catalogue with persona and online gating, zizmor.yml schema and discovery rules, exit-code semantics, auto-fix blast radius, and the CI and pre-commit templates.
This command is interactive by default. With no arguments, run the three-layer wizard below. Never dump a raw zizmor invocation and stop — the useful output is a triaged verdict, not a finding list.
Ownership boundary (enforced at the menu)
| Question | Authoritative command |
|---|---|
| "Is this workflow valid?" (syntax, schema, shell bugs) | /platform-skills:github-actions — actionlint |
| "Is this workflow safe?" (injection, permissions, pinning) | this command |
"Is my action.yml well designed?" |
/platform-skills:composite-actions |
| "How do I keep these SHA pins current?" | /platform-skills:renovate |
| "Is there a misconfig in my Terraform / Helm / Dockerfile?" | /platform-skills:checkov |
| "Does this image or dependency have CVEs?" | /platform-skills:trivy |
| "How do I sign images / generate an SBOM?" | /platform-skills:supply-chain |
Zizmor and actionlint are complements. A workflow can be perfectly valid and still hand an attacker a shell. When the user asks for "workflow checks" without qualifying, run both and say which tool produced which finding.
Mode dispatch
Parse the first word of $ARGUMENTS as the mode. When $ARGUMENTS is empty, run the three-layer interactive wizard.
| Mode | What it does |
|---|---|
scan |
Default-persona audit of the current repo — the everyday run |
audit |
Deep sweep: --persona=auditor --min-confidence=low, all collectors, online |
fix |
--fix=safe (or all on request), show the diff, re-audit what remains |
triage |
Walk existing findings one at a time → fix / inline-ignore / config-ignore / remap / disable |
config |
Generate or repair .github/zizmor.yml — pinning policy, allowlists, suppressions |
ci |
Emit the GitHub Actions workflow — SARIF alerts, hard-fail gate, or both |
precommit |
Add the zizmor-pre-commit hook and explain the offline caveat |
explain |
Explain one audit id or one finding, and how to fix it properly |
| (empty) | Three-layer interactive wizard |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- today Changed · +1 lines f0542ccab429
- 7d ago First seen · 396 lines · 175 tokens per session scan A 775fe704a169
zizmor is a skill published in the GitHub repository nitinjain999/platform-skills (70 stars, last pushed today), licensed Apache-2.0. It adds 175 tokens to every session and 6,274 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-12.
Other skills, from other repositories
aw-author
Author, validate, and improve GitHub Agentic Workflow (gh-aw) markdown files. Use when the user wants to create a new workflow, validate an existing workflow, improve a workflow, or debug workflow issues. Triggers on: "aw-author", "agentic workflow", "gh-aw workflow", "workflow markdown", "workflow frontmatter"…
devops
Use when setting up CI/CD pipelines, deploying applications, managing cloud infrastructure (AWS, GCP, Azure), implementing monitoring, containerizing services, or automating deployments with infrastructure as code.
complete-infra
Complete infrastructure task — lint, validate, review, and submit PR. Use when an infrastructure-only branch is ready for submission — runs Terraform/Helm validation and creates the PR, skipping application/frontend checks.
infra-plan
Plan infrastructure changes — Terraform modules, Helm charts, CI/CD pipelines. Use when the user wants to add or modify cloud infrastructure, Kubernetes resources, or deployment pipelines.
infrastructure-planning
Plan and document the required software, infrastructure, and logistics for a Paperclip company — domains, GitHub, Docker Hub, Kubernetes, Slack, Google Workspace, Stripe, shipping providers, and CI/CD pipelines. Use when setting up infrastructure for a new company or auditing what an existing company needs.
operating-github-ci-fixer
Use when the user asks OpenSRE to fix failing GitHub CI, GitHub Actions checks, failing pull request checks, a broken PR branch, or CI on a named branch such as main.