A generator for GitHub Actions workflows, which are automated jobs that run checks when code changes. It creates CI, or continuous integration, workflows based on the repository's detected programming stack and project profile.

It helps set up linting, type checking, tests, pull-request health checks, and repository governance checks in GitHub Actions.

It removes the need to write the workflow configuration manually and helps match automated checks to the project's existing quality rules.

gen-ci — Skill for Claude Code by thettwe

Install

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.

Any agent

npx skills add thettwe/nyann --skill gen-ci

Clone the repo

git clone --depth 1 https://github.com/thettwe/nyann

Made for: Claude Code.

Or install nyann, the plugin that ships this one along with the rest of its 41 skills, 41 commands, 3 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/thettwe/nyann/gen-ci/github.svg)](https://agentmods.dev/skills/thettwe/nyann/gen-ci)

Your own site

<a href="https://agentmods.dev/skills/thettwe/nyann/gen-ci"><img src="https://agentmods.dev/badge/skills/thettwe/nyann/gen-ci/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/thettwe/nyann/gen-ci"><img src="https://agentmods.dev/badge/skills/thettwe/nyann/gen-ci.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 141 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,346 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00141	$0.01346
Opus 5	$0.00071	$0.00673
Sonnet 5	$0.00028	$0.00269
Haiku 4.5	$0.00014	$0.00135

Measured 9d ago against content hash 6262e3cfef06, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

gen-ci 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 9d ago.

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.

skills/gen-ci/SKILL.md · 113 lines

How it starts

The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.

gen-ci — Generate GitHub Actions CI Workflow

You are the gen-ci skill. You generate a GitHub Actions CI workflow that mirrors the project's quality gates (lint, typecheck, test) based on the detected stack and nyann profile.

When to trigger

User asks to generate CI, add GitHub Actions, create a CI workflow, or set up CI/CD
User asks to add continuous integration, create a pipeline, or add a lint+test workflow
User asks to add a governance check, PR health check, drift check to CI, or governance gate
User is bootstrapping a new project and wants CI

DO NOT trigger on: general questions about CI/CD concepts, debugging existing workflows not managed by nyann, or requests to modify workflows outside nyann markers.

Execution flow

Phase 1: Detect stack and resolve profile

Run bin/detect-stack.sh --path . to get a StackDescriptor JSON.
Resolve and load the active profile via bin/load-profile.sh <name> (resolves preferences → CLAUDE.md markers → "default" fallback).

Phase 2: Preview the workflow

Run bin/gen-ci.sh --profile <profile> --stack <stack> --target . --dry-run to preview the generated workflow.
Show the user what will be generated:
- Template selected (typescript/python/go/rust/generic)
- Jobs and steps (lint, typecheck, test)
- Package manager and version matrix
- Path filters (if monorepo)

Phase 2.5: Offer governance check

If the profile has a governance block, or if the user mentioned "governance", "health check", or "drift check", offer to also generate the governance-check workflow:

"Also generate a governance check that runs doctor on every PR and posts a health report comment? (adds governance-check.yml)"

If the user accepts (or originally asked for it), add --governance to the gen-ci.sh invocation.

Phase 3: Confirm and write

Ask the user: "Write this CI workflow to .github/workflows/ci.yml?"

On confirmation, run:

bin/gen-ci.sh --profile <profile> --stack <stack> --target . [--governance]

Report what was written (ci.yml, and governance-check.yml if --governance).

Read the full file on GitHub · 113 lines

Changes

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.

9d ago First seen · 113 lines · 141 tokens per session scan A 6262e3cfef06

Subscribe to this mod's changes

gen-ci is a skill published in the GitHub repository thettwe/nyann (6 stars, last pushed 10d ago), licensed MIT. It adds 141 tokens to every session and 1,346 once invoked, about $0.0007 per session on Opus 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-08-31.

CI and CD Claude Code DevOps and cloud claude-code-plugin claude-skills github governance scaffolding

deploy

Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays. Use when configuring Fly.io, Docker, CI/CD, health checks, or production migrations.

oliver-kriska/claude-elixir-phoenix · 46 tokens

go-tooling-security

Use when setting up Go modules/workspaces, configuring golangci-lint v2, running govulncheck, or building a Go CI quality gate. Not for app logic or non-Go audits.

fusengine/agents · 46 tokens

rust-tooling-cicd

Use when structuring a Cargo workspace or building a Rust CI pipeline — fmt, clippy, cargo-deny/audit, nextest, coverage, MSRV. Not for writing the tests themselves (rust-testing-quality).

fusengine/agents · 51 tokens

Solana Squads Upgrade

This skill should be used when the user asks to "upgrade a Solana program through Squads", "set up squads multisig deployment", "create a Squads upgrade proposal", "configure squads-program-action", "deploy via Squads multisig", "set up Squads CI/CD pipeline", "squads GitHub Actions workflow", or mentions Solana…

widnyana/eyay-toolkits · 89 tokens

ci-workflow

Design and maintain .NET CI workflows for F#, C#, and mixed solutions with SDK setup, restore, build, test, format checks, package checks, caching, and matrix decisions.

gaelic-ghost/socket · 41 tokens

devex

Use when improving developer workflows, setting up or optimising CI/CD pipelines, reducing build times, improving local development setup, evaluating developer tooling, writing internal documentation for engineers, measuring developer productivity, or any task focused on making the engineering team faster and less…

pranav8494/team-of-agents · 55 tokens