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 girijashankarj/cursor-handbook --skill ci-cdgit clone --depth 1 https://github.com/girijashankarj/cursor-handbookWrote 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/girijashankarj/cursor-handbook/ci-cd)<a href="https://agentmods.dev/skills/girijashankarj/cursor-handbook/ci-cd"><img src="https://agentmods.dev/badge/skills/girijashankarj/cursor-handbook/ci-cd.svg" alt="Measured on agentmods" 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.00027 | $0.00510 |
| Opus 5 | $0.00014 | $0.00255 |
| Sonnet 5 | $0.00005 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
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 5d 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.
What it actually says
Skill: Set Up CI/CD Pipeline
Trigger
When the user needs to set up or modify CI/CD pipelines.
Steps
Step 1: Define Pipeline Stages
- Lint and format check
- Type check:
{{CONFIG.testing.typeCheckCommand}} - Unit tests:
{{CONFIG.testing.testCommand}} - Build
- Integration tests
- Security scan
- Deploy
Step 2: Create Pipeline Configuration
- Create workflow file (
.github/workflows/ci.ymlfor GitHub Actions) - Define trigger events (push, PR, schedule)
- Configure job runners and environments
- Set up caching for dependencies
Step 3: Configure Secrets
- List required secrets
- Add to CI/CD secrets store (never in code)
- Document required secrets in README
Step 4: Add Quality Gates
- Tests must pass (0 failures)
- Coverage ≥ {{CONFIG.testing.coverageMinimum}}%
- No type errors
- No critical security vulnerabilities
- Build succeeds
Step 5: Set Up Deployment
- Configure environment promotion (dev → staging → prod)
- Add manual approval for production
- Configure rollback triggers
- Set up smoke tests post-deployment
Step 6: Test Pipeline
- Trigger on a test branch
- Verify all stages complete
- Verify failure handling (intentionally break a stage)
- Verify notifications work
If a step fails
| Step | Failure | Recovery |
|---|---|---|
| Step 4 | Quality gate blocks pipeline | Fix failing tests, coverage, or type errors locally; do not lower thresholds to pass |
| Step 5 | Deploy stage fails | Check secrets and env vars; verify target environment is reachable; rollback if prod deploy partially applied |
| Step 6 | Pipeline fails on test trigger | Fix the broken stage; verify failure handling works (pipeline should fail fast, not deploy on failure) |
Never remove manual approval for production. Never deploy on failure.
Completion
CI/CD pipeline is running, tested, and documented.
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.
- 5d ago First seen · 64 lines · 27 tokens per session scan A 16edbb4d1c89
ci-cd is a skill published in the GitHub repository girijashankarj/cursor-handbook (30 stars, last pushed 8d ago), licensed MIT. It adds 27 tokens to every session and 510 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
audit-gate-logic
Read-only audit of CI gate logic — silent bypass, ratchet gaming, required-but-not, duplicate gates. Use when "can CI be bypassed" or "why did a regression pass CI". Cost → audit-cicd. Consolidation → housekeep-gates. Rule content → audit-doctrine.
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
octocode-benchmark
Use when planning, running, grading, or reporting the by-hand Octocode research benchmark — pairwise matchups (Octocode anchor vs one baseline: gh+RTK, gh+Headroom, or plain gh) over markdown questions, with a fresh isolated runner agent per (question, arm, pass), one blind judge per question grading two answers X/Y…
patrol-e2e-testing
Use when writing E2E/integration tests, testing native interactions like permissions or system dialogs, capturing UI regressions, or validating cross-platform behavior (Patrol 4.x).
testing
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.
mockito
Use when generating mocks, stubbing methods, verifying interactions, capturing arguments, or choosing between mocks, fakes, and real objects (Mockito).