4,519 mods in this category, of every kind an
agent can take. Each one carries what it costs per session, what the
scan found, and whether it is the original.
Diagnose and fix red CI on zaxy — fetch the right logs, reproduce locally despite the known local quirks (testdoctor hang, benchmark tables), do coverage-ratchet math correctly, and apply the test-vs-source intent rule. Use when CI is red, a check fails on a PR, "make master green", or coverage ratchet fails.
Add Cloudflare Workers preview deployments to existing GitHub apps using GitHub Actions, Wrangler, gh secrets, and the GitHub Deployments API. Use when asked to add per-PR preview deployments, ephemeral Workers previews, preview URLs, GitHub deployment statuses, Cloudflare preview environments, or teardown on PR close.
Instructions for sbom-tool/gh-guard, covering gh-guard: ci/cd supply chain hardening for rust, what this plugin does, hardening levels, commands and skills (contextual knowledge).
Wait for CI to settle across all repos in a Polygraph session, then report results and investigate failures. USE WHEN user says "await polygraph", "wait for polygraph ci", "polygraph ci status", "check polygraph ci", "watch polygraph session", "monitor polygraph".
Claude Code instructions for smykla-skalski/klaudiush, covering claude.md, project overview, commands, completion (shell completion scripts) and doctor (diagnose setup and configuration).
Instructions for RayFernando1337/ray-fernando-actions-templates, covering agents.md — adopt these ci templates in a consumer repo, 1. purpose & how to use this repo, 2. workflow catalog — when to adopt each, 3. required secrets / vars (names only) and almost always.
Assess and enhance software projects for enterprise-grade security, quality, and automation. This skill should be used when evaluating projects for production readiness, implementing supply chain security (SLSA, signing, SBOMs), hardening CI/CD pipelines, establishing quality gates, reviewing code or PRs, writing…
You are an expert CI/CD automation agent responsible for running the complete test suite that mirrors the GitHub Actions CI workflow when code is pushed to origin. Your primary function is to execute tests reliably, monitor their progress, and report comprehensive results.
GitHub Actions best practices — current action versions, caching, security, and common patterns. Activate when writing or modifying GitHub Actions workflows.
Attack patterns and real-world examples sourced from the HackerBot Claw campaign analysis by StepSecurity (2025): https://www.stepsecurity.io/blog/hackerbot-claw-github-actions-exploitation -->.
Add zizmor (GitHub Actions security analysis) CI to a repository and fix every finding it surfaces. Use when asked to "add zizmor", harden a repo's GitHub Actions workflows, pin actions to SHAs, or make workflows pass a security audit. Adds a zizmor workflow + a dependabot config (on the default branch; other branches…
Instructions for ai4curation/github-ai-integrations: This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment.
Update and deploy the Dash Sylvereye docs site at https://dashsylvereye.observatoriogeo.mx via the GitHub Pages workflow (.github/workflows/docs-deploy.yml). Use whenever the user wants to deploy, redeploy, ship, push, publish, or update the docs site to production / Pages / live, AND whenever the user wants to check…
Investigate CI/Prow job failures on a GitHub pull request. Use when the user pastes a PR URL and asks about CI failures, red checks, test failures, or wants to understand why a job failed.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: