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.
curl -O https://raw.githubusercontent.com/aiblueprinthq/ai-blueprint/main/.agents/skills/ci/SKILL.mdgit clone --depth 1 https://github.com/aiblueprinthq/ai-blueprintWrote 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/aiblueprinthq/ai-blueprint/ci)<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.
<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>- NVIDIA SkillSpector pass
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.02000 |
| Opus 5 | $0.00032 | $0.01000 |
| Sonnet 5 | $0.00013 | $0.00400 |
| Haiku 4.5 | $0.00006 | $0.00200 |
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 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 — 202 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 using the dashboard activity
contract in AGENTS.md.
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-verifyskips 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.
Step 1 - inspect without changing files
Read enough to identify the real project setup:
AGENTS.md, especially Commands and any documentedVerifycommand- package or language manifests and task-runner files
- lockfiles and the package manager they imply
- existing typecheck, test, build, lint, and other quality commands
- test configuration and actual test files
- runtime version files such as
.nvmrc,.node-version,.python-version,go.mod, orrust-toolchain.toml .github/workflows/and any documented external CI- git's current branch, configured default branch, and remotes when available
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 · +31 lines · +14 tokens per session c3725f11c532
- 7d ago Changed · +7 lines 4991ed58ba4a
- 8d ago Changed · +2 lines · -55 tokens per session 2bb1148f1607
- 12d ago First seen · 162 lines · 104 tokens per session scan A 2b4acc7473e2
ci is a skill published in the GitHub repository aiblueprinthq/ai-blueprint (399 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 2,000 once invoked, about $0.0003 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-30.
Other skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.