Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/itallstartedwithaidea/agent-skillsnpx agentmods add skills/itallstartedwithaidea/agent-skills/ci-cd-pipelinesWrote 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/itallstartedwithaidea/agent-skills/ci-cd-pipelines)<a href="https://agentmods.dev/skills/itallstartedwithaidea/agent-skills/ci-cd-pipelines"><img src="https://agentmods.dev/badge/skills/itallstartedwithaidea/agent-skills/ci-cd-pipelines/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/itallstartedwithaidea/agent-skills/ci-cd-pipelines"><img src="https://agentmods.dev/badge/skills/itallstartedwithaidea/agent-skills/ci-cd-pipelines.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.00038 | $0.01445 |
| Opus 5.5 | $0.00015 | $0.00578 |
| Sonnet 5.5 | $0.00008 | $0.00289 |
| Haiku 4.5 | $0.00004 | $0.00145 |
Grade A, and why
ci-cd-pipelines 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD Pipelines
Part of Agent Skills™ by googleadsagent.ai™
Description
CI/CD Pipelines defines production-grade continuous integration and deployment workflows using GitHub Actions with wrangler deploy, link validation, HTML validation, and automated quality gates. This skill encodes the actual CI/CD patterns used by googleadsagent.ai™ to deploy Workers, validate 18,000+ pages of generated content, and maintain zero-downtime production releases.
A CI pipeline is only as valuable as its gates. This skill goes beyond "run tests and deploy" to include HTML validation (no broken markup in generated pages), internal link checking (no dead links across the city × service matrix), structured data validation (JSON-LD schema compliance), and Lighthouse performance audits. Every merge to main triggers a cascade of validation steps that catch regressions before they reach production.
The deployment pipeline implements progressive rollout: deploy to a staging environment first, run the full validation suite against staging, promote to production only on green, and maintain instant rollback capability via wrangler rollback. Preview deployments for pull requests give reviewers a live URL to test changes before approval.
Use When
- Setting up CI/CD for Cloudflare Workers or Pages projects
- Adding HTML validation or link checking to a pipeline
- Implementing progressive deployment with staging and production
- Automating quality gates for content-heavy sites
- Configuring preview deployments for pull requests
- Building rollback capability into deployment workflows
How It Works
graph TD
A[Push to Branch] --> B[GitHub Actions Trigger]
B --> C[Install Dependencies]
C --> D[Run Unit Tests]
D --> E[Run Type Checking]
E --> F{Branch?}
F -->|PR| G[Deploy to Preview]
F -->|main| H[Deploy to Staging]
G --> I[Run Link Checker on Preview]
H --> J[Run Full Validation Suite]
J --> K[HTML Validation]
J --> L[Link Checking]
J --> M[JSON-LD Validation]
J --> N[Lighthouse Audit]
K --> O{All Green?}
L --> O
M --> O
N --> O
O -->|Yes| P[Promote to Production]
O -->|No| Q[Block + Notify]
I --> R[Comment PR with Preview URL]
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.
- 1mo ago First seen · 165 lines · 38 tokens per session scan A d4845e89bf37
ci-cd-pipelines is a skill published in the GitHub repository itallstartedwithaidea/agent-skills (44 stars, last pushed 6mo ago), licensed MIT. It adds 38 tokens to every session and 1,445 once invoked, about $0.0002 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.
Other skills, from other repositories
deploy-and-runtime-verification
MANDATORY deploy after every code change. Typecheck → deploy → purge CDN → E2E on production → visual verify → fix-forward loop. Workers Builds native CI/CD, D1 Time Travel PIT recovery, D1→R2 long-term backups, wrangler rollback, wrangler secrets management, structured observability, cross-browser smoke tests…
ci-cd-pipelines
CI/CD Pipelines defines production-grade continuous integration and deployment workflows using GitHub Actions with wrangler deploy, link validation, HTML validation, and automated quality gates.
secret-protection
Secret Protection prevents credential leaks across the development lifecycle through .env scanning, pre-commit hooks, secret rotation policies, and runtime detection.
diagnose-github-actions
Diagnose a public GitHub Actions workflow run with RunVerdict before changing code or rerunning CI. Use when a GitHub Actions run, job, matrix shard, test suite, build, lint, dependency install, timeout, runner, authentication, or infrastructure step failed and the agent needs evidence-linked root causes…
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.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.