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 agentmods add skills/srstomp/pokayokay/ci-cdnpx skills add srstomp/pokayokay --skill ci-cdgit clone --depth 1 https://github.com/srstomp/pokayokayWrote 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/srstomp/pokayokay/ci-cd)<a href="https://agentmods.dev/skills/srstomp/pokayokay/ci-cd"><img src="https://agentmods.dev/badge/skills/srstomp/pokayokay/ci-cd.svg" alt="Measured on agentmods" 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 | $0.00057 | $0.00806 |
| Opus 5 | $0.00028 | $0.00403 |
| Sonnet 5 | $0.00011 | $0.00161 |
| Haiku 4.5 | $0.00006 | $0.00081 |
Grade A, and why
ci-cd 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 4d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD Expert
Create, debug, and optimize CI/CD pipelines across platforms.
Platform Selection
| Platform | Best For | Key Strength |
|---|---|---|
| GitHub Actions | GitHub repos, open source | Marketplace, native integration |
| GitLab CI | GitLab repos, self-hosted | Built-in registry, Auto DevOps |
| CircleCI | Complex workflows, speed | Parallelism, orbs |
| Azure DevOps | Microsoft/enterprise | Azure integration, YAML templates |
| Bitbucket | Atlassian stack | Jira integration, pipes |
Key Principles
- Security first: Never expose secrets in logs, use environment-specific secrets
- Reliability: Idempotent steps, deterministic builds, pinned dependency versions
- Efficiency: Cache aggressively, parallelize independent jobs, skip unchanged paths
- Maintainability: DRY with reusable workflows/templates, clear naming
Quick Start Checklist
- Choose platform based on repository hosting
- Create pipeline with lint → test → build → deploy stages
- Configure secrets and environment variables
- Set up caching for dependencies and build artifacts
- Add deployment strategy (blue-green recommended for production)
- Review security checklist before going live
References
| Reference | Description |
|---|---|
| github-actions-basics.md | Workflows, triggers, jobs, steps, services |
| github-actions-advanced.md | Reusable workflows, composite actions, security, complete example |
| gitlab-ci-basics.md | Pipeline structure, triggers, jobs, caching, artifacts, variables |
| gitlab-ci-advanced.md | Templates, includes, rules, Docker-in-Docker, security scanning |
| circleci-basics.md | Config structure, executors, jobs, commands, caching, artifacts |
| circleci-advanced.md | Workflows, orbs, conditionals, Docker builds, complete example |
| azure-devops-basics.md | Pipeline structure, triggers, agents, variables, tasks, caching |
| azure-devops-advanced.md | Templates, environments, deployments, conditions, containers |
| bitbucket-pipelines-basics.md | Pipeline types, steps, caching, artifacts, variables |
| bitbucket-pipelines-advanced.md | Pipes, Docker, YAML anchors, deployments, complete example |
| deployment-strategies-blue-green-canary.md | Blue-green and canary deployments with K8s and AWS examples |
| deployment-strategies-rolling-flags-rollback.md | Rolling deploys, feature flags, rollback, health checks |
| debugging-error-categories.md | Environment, permission, network, resource, timing, cache, Docker errors |
| debugging-platform-fixes.md | Platform-specific debugging, common fix patterns, quick reference |
| security-checklist.md | Secrets, permissions, supply chain security |
What ships with it
16 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/azure-devops-advanced.md 7.4 KB
- references/azure-devops-basics.md 6.1 KB
- references/bitbucket-pipelines-advanced.md 7.9 KB
- references/bitbucket-pipelines-basics.md 6.2 KB
- references/circleci-advanced.md 8.4 KB
- references/circleci-basics.md 5.2 KB
- references/debugging-error-categories.md 7.1 KB
- references/debugging-platform-fixes.md 3.7 KB
- references/deployment-strategies-blue-green-canary.md 12 KB
- references/deployment-strategies-rolling-flags-rollback.md 7.4 KB
- references/github-actions-advanced.md 6.8 KB
- references/github-actions-basics.md 6.0 KB
- references/gitlab-ci-advanced.md 5.1 KB
- references/gitlab-ci-basics.md 5.3 KB
- references/security-checklist.md 11 KB
- scripts/validate-workflow.sh 8.0 KB runs code
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.
- 4d ago First seen · 55 lines · 57 tokens per session scan A 40e6714f2737
ci-cd is a skill published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 2mo ago), licensed MIT. It adds 57 tokens to every session and 806 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…