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 rules/girijashankarj/cursor-handbook/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/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.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.00516 | $0.00516 |
| Opus 5 | $0.00258 | $0.00258 |
| Sonnet 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 today.
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.
- today 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 (30 stars, last pushed 4d ago), licensed MIT. It adds 516 tokens to every session, about $0.0026 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 cursor rules, from other repositories
graphstack
GraphStack v4.7.1 — Orchestrated, graph-first, GNAP-tracked AI development (cross-platform).
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
mcp
Guidelines for implementing and interacting with the Task Master MCP Server.
commands
Guidelines for implementing CLI commands using Commander.js.
git_workflow
Git workflow integrated with Task Master for feature development and collaboration.
hamster
Guidelines for implementing tasks imported from Hamster using Task Master CLI.