A setup procedure for automatic checks on GitHub, a service for hosting code and reviewing changes. It uses one documented Verify command for the project's existing type checks, tests, and build.

For detecting the project's tools and existing workflows, preserving current CI, configuring GitHub Actions, and running the Verify command locally. It does not change merge rules, push code, deploy, or add local hooks.

It keeps local checks and GitHub pull-request checks based on the same recipe, reducing differences between a developer's machine and the automated check.

How aiblueprinthq/ai-blueprint configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to aiblueprinthq/ai-blueprint. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/aiblueprinthq/ai-blueprint/main/.agents/skills/ci/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/aiblueprinthq/ai-blueprint

Made for: Claude Code, Codex.

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/aiblueprinthq/ai-blueprint/ci/github.svg)](https://agentmods.dev/skills/aiblueprinthq/ai-blueprint/ci)

Your own site

<a href="https://agentmods.dev/skills/aiblueprinthq/ai-blueprint/ci"><img src="https://agentmods.dev/badge/skills/aiblueprinthq/ai-blueprint/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/aiblueprinthq/ai-blueprint/ci"><img src="https://agentmods.dev/badge/skills/aiblueprinthq/ai-blueprint/ci.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,150 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00063	$0.02150
Opus 5.5	$0.00025	$0.00860
Sonnet 5.5	$0.00013	$0.00430
Haiku 4.5	$0.00006	$0.00215

Measured 7d ago against content hash a71675a13770, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

.agents/skills/ci/SKILL.md · 209 lines

How it starts

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

ci - set up automatic GitHub checks

Context reuse: Reuse any required file already loaded in project instructions or the current session. Read it again only if absent, changed, or exact current bytes or line references are needed.

First action: Before project inspection, preflight, or any other tool call, publish running to blueprint/.state/run.json when blueprint/.state/ exists. From the project root, run the first helper that exists, node .agents/skills/blueprint-doctor/scripts/run-state.mjs or node .claude/skills/blueprint-doctor/scripts/run-state.mjs, with start --command <skill> --summary "<truthful summary>" --boundary <read-only|reviewed|local-only>. Use update at milestones, with --status blocked --resume <command> for a blocker, and finish --status ready|completed at the end; --help lists every option and blueprint/workflow.md has the full activity contract. A missing or failing helper is a warning, not a blocker.

Where this sits in the workflow:

/onboard or /adopt  ->  [ci]  ->  Verify locally  ->  GitHub runs Verify
(project commands)     (setup)    (same recipe)      (pull requests)

This skill gives local work and GitHub one shared automated command. It is an optional setup task, not a requirement for using the Blueprint.

Keep the beginner explanation simple:

Verify is the recipe. It runs checks the project already has.
GitHub Actions is the worker. It runs the same recipe automatically.
A GitHub ruleset is the lock. That optional remote setting can require the worker to report green before merge.
A pre-push hook is the early warning. That optional local setting runs the recipe before a push leaves the machine. It is a convenience, not the lock: git push --no-verify skips it.

This skill configures the recipe and worker, and adds the hook only when the user opts in. It never changes the remote ruleset, pushes, publishes, or deploys.

Input

No argument is required. A named provider or workflow preference is a request to review, not permission to replace existing CI. This skill's default provider is GitHub Actions because it creates GitHub pull-request checks.

Read the full file on GitHub · 209 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.

7d ago Changed · +7 lines a71675a13770
1mo ago Changed · +31 lines · +14 tokens per session c3725f11c532
2mo ago Changed · +7 lines 4991ed58ba4a
2mo ago Changed · +2 lines · -55 tokens per session 2bb1148f1607
2mo ago First seen · 162 lines · 104 tokens per session scan A 2b4acc7473e2

Subscribe to this mod's changes

ci is a skill published in the GitHub repository aiblueprinthq/ai-blueprint (493 stars, last pushed 7d ago), licensed MIT. It adds 63 tokens to every session and 2,150 once invoked, about $0.0003 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-08-30.

CI and CD DevOps and cloud

ci next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
ciaiblueprinthq/ai-blueprint	Skill	493	7d ago	MIT	A	63	Claude Code, Codex
chinese-git-workflowjnMetaCode/superpowers-zh	Skill	8.5k	11d ago	MIT	A	69	Claude Code
atmos-profilescloudposse/atmos	Skill	1.4k	yesterday	Apache-2.0	A	35	Claude Code
webhook-managementhoangsonww/Claude-Code-Agent-Monitor	Skill	1.1k	yesterday	MIT	A	56	Claude Code, Codex
monorepo-managementwshobson/agents	Skill	42k	yesterday	MIT	C	54	Claude Code
managing-github-actions-secretsPostHog/posthog-foss	Skill	728	yesterday	MIT	A	67	Claude Code, Codex
postman-newman-automationLambdaTest/agent-skills	Skill	390	yesterday	MIT	A	156	Claude Code, Codex

ai-blueprint: Skill for Claude Code