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.
npx skills add byerlikaya/claude-starter-kit --skill ci-pipelinegit clone --depth 1 https://github.com/byerlikaya/claude-starter-kitWrote 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/byerlikaya/claude-starter-kit/ci-pipeline)<a href="https://agentmods.dev/skills/byerlikaya/claude-starter-kit/ci-pipeline"><img src="https://agentmods.dev/badge/skills/byerlikaya/claude-starter-kit/ci-pipeline/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/byerlikaya/claude-starter-kit/ci-pipeline"><img src="https://agentmods.dev/badge/skills/byerlikaya/claude-starter-kit/ci-pipeline.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.00030 | $0.00606 |
| Opus 5 | $0.00015 | $0.00303 |
| Sonnet 5 | $0.00006 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
ci-pipeline 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 11d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Pipeline
Trigger phrases: "ci", "pipeline", "github actions", "jenkins", "build pipeline", "pr gate", "pr check", "build fail", "build broke", "ci is failing", "workflow"
Stages (fail-fast — stop if it breaks early)
- Lint / format — style and static analysis
- Build — 0 warnings / 0 errors
- Test — unit + integration, coverage collected
- Quality —
sonarqube-checkquality gate - Security —
dependency-audit+security-scan(where applicable) - Artifact / packaging — (deployment is separate,
deploy)
Principles
- Deterministic: dependencies pinned, cache keyed correctly; no "it worked on my machine".
- Secret management: CI secret store; NO plaintext secrets in the repo/logs (overlaps with trace scan).
- PR gate: quality gate + tests must pass; a red build is not merged.
- Branch protection: direct push to main is disabled; PR + review required.
When a stage fails
- Fetch the failing job's log first —
gh run view --log-failed,glab ci trace,jenkins-cli console <job>, whichever this project's host provides — and quote the failing lines: a status icon names which job broke, never why. Log unreachable (no access, retention expired, the job never started) → report exactly that; never infer the cause. - Reproduce with the exact command the pipeline runs, copied out of the CI config — same flags, same env, same
versions. Green locally is not a pass: the environment difference is now the defect, so take it to
systematic-debugging. - A re-run is not a fix. Re-running until it passes hides the cause; re-run only to establish that a failure is
intermittent — and an intermittent failure in this repo's own suite is a bug (
testing), not a retry. - Say which failures aren't yours. A required check owned by another change, or an external service that was down, is reported out of scope with the job named — silence about it reads as a clean run.
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.
- 11d ago First seen · 41 lines · 30 tokens per session scan A 1ad148dc5aca
ci-pipeline is a skill published in the GitHub repository byerlikaya/claude-starter-kit (22 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 606 once invoked, about $0.0002 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
verification-engine
Use when verifying build/test/lint before commit, PR, or completion claims. Runs verification pipeline in fresh subagent context with auto-repair. Triggers on /handoff-verify, pre-commit check, build verification, test validation.
verify-implementation
A workflow that runs a project’s verification skills to produce a report on coding patterns, architecture rules, and project conventions. It is intended for work after implementation, before a pull request, or during code review.
ci-pipeline-patterns
GitHub Actions workflow templates, matrix builds, caching, and monorepo CI strategies.
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.
devops-cloud
DevOps, cloud infrastructure, and platform engineering. Use when working with AWS, GCP, Azure, Kubernetes, Terraform, CI/CD pipelines, or infrastructure as code.
test-e2e
End-to-end infrastructure pipeline validation across Terraform and Ansible repos.