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.
git 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/rules/girijashankarj/cursor-handbook/ci-cd)<a href="https://agentmods.dev/rules/girijashankarj/cursor-handbook/ci-cd"><img src="https://agentmods.dev/badge/rules/girijashankarj/cursor-handbook/ci-cd/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/rules/girijashankarj/cursor-handbook/ci-cd"><img src="https://agentmods.dev/badge/rules/girijashankarj/cursor-handbook/ci-cd.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.00516 | $0.00516 |
| Opus 5.5 | $0.00206 | $0.00206 |
| Sonnet 5.5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00052 | $0.00052 |
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 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD Rules
Pipeline Stages
1. Lint & Format Check → 2. Type Check → 3. Unit Tests → 4. Build → 5. Integration Tests → 6. Security Scan → 7. Deploy
Stage Details
| Stage | Tool | Fail Condition |
|---|---|---|
| Lint | {{CONFIG.techStack.linter}} | Any errors |
| Type Check | {{CONFIG.testing.typeCheckCommand}} |
Any type errors |
| Unit Tests | {{CONFIG.testing.testCommand}} |
<{{CONFIG.testing.coverageMinimum}}% coverage or failures |
| Build | Package manager build | Build failure |
| Integration | Integration test suite | Any failures |
| Security | npm audit / Snyk / Trivy |
Critical vulnerabilities |
| Deploy | CD tool | Deployment failure |
Branch Strategy
main— production-ready codedevelop— integration branch{{CONFIG.conventions.branchPrefix.feature}}*— new features{{CONFIG.conventions.branchPrefix.bugfix}}*— bug fixes{{CONFIG.conventions.branchPrefix.hotfix}}*— production hotfixes{{CONFIG.conventions.branchPrefix.release}}*— release preparation
Deployment Rules
- NEVER deploy directly to production without CI passing
- Use blue/green or canary deployments for zero downtime
- Automated rollback on health check failure
- Database migrations run before code deployment
- Feature flags for gradual rollouts
- Smoke tests after every deployment
Commit Convention ({{CONFIG.conventions.commitFormat}})
<type>(<scope>): <description>
Types: feat, fix, docs, style, refactor, test, chore, perf, ci
Scope: module or feature name
Description: imperative mood, lowercase, no period
Examples:
feat(orders): add order cancellation endpoint
fix(auth): handle expired refresh tokens
test(payments): add integration tests for refund flow
Docker
- Multi-stage builds for minimal image size
- Non-root user in production containers
- Pin base image versions (no
latesttag) - Use
.dockerignoreto exclude unnecessary files - Health check endpoint in every service
- Scan images for vulnerabilities before deployment
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 · 61 lines · 516 tokens per session scan A 72ed6b2b81aa
ci-cd is a cursor rule published in the GitHub repository girijashankarj/cursor-handbook (33 stars, last pushed 1mo ago), licensed MIT. It adds 516 tokens to every session, about $0.0021 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-09-03.
Other cursor rules, from other repositories
ci-cd
CI/CD: pipelines, deployment, automation.
tooling-for-apps
ArchiPy app tooling — uv dependencies, project checks, Behave, Ruff, ty, and pre-commit.
yaml-config
Rules for YAML / config / infra files (Docker, K8s, Terraform, GitHub Actions, etc.).
roslyn-mcp-ci
GitHub Actions test jobs; do not serialize the full suite again.
approved-plan-execution
Guard execution of an approved plan or burndown: forbid reward hacking and feature deletion; require checkpoints, context discipline, safe terminal use, and fresh verification. Applies to approved plan-.md, complete-everything, and burndown-full runs, whatever model runs them.
verification-before-completion
Require fresh, scope-appropriate evidence before any completion claim. Distinguishes implemented, locally verified, repository-green, PR-green, deployed, and observed-stable states.