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/nedcodes-ok/cursorrules-collectionWrote 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/nedcodes-ok/cursorrules-collection/ci-cd)<a href="https://agentmods.dev/rules/nedcodes-ok/cursorrules-collection/ci-cd"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/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/nedcodes-ok/cursorrules-collection/ci-cd"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/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.00234 | $0.00234 |
| Opus 5.5 | $0.00094 | $0.00094 |
| Sonnet 5.5 | $0.00047 | $0.00047 |
| Haiku 4.5 | $0.00023 | $0.00023 |
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.
What it actually says
CI/CD Rules
Pipeline Design
- Keep pipelines fast — under 10 minutes for feedback
- Run cheap checks first: lint → type check → unit tests → integration
- Cache dependencies between runs
- Use parallel stages for independent jobs
Testing in CI
- Run the full test suite on every PR
- Use separate stages: build → test → deploy
- Fail fast — stop pipeline on first failure
- Report test results and coverage in PR comments
Deployment
- Use the same artifact for all environments
- Deploy to staging before production
- Use feature flags for gradual rollouts
- Automate rollbacks with health checks
Security
- Never hardcode secrets in pipeline configs
- Use CI platform's secret management
- Scan dependencies for vulnerabilities in CI
- Sign artifacts and verify signatures before deployment
Best Practices
- Pin CI runner/action versions
- Use matrix builds for multi-platform/version testing
- Keep pipeline configs DRY — use templates/reusable workflows
- Monitor pipeline metrics (duration, failure rate)
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 · 37 lines · 234 tokens per session scan A 3ba6cf14bf23
ci-cd is a cursor rule published in the GitHub repository nedcodes-ok/cursorrules-collection (38 stars, last pushed 7mo ago), licensed MIT. It adds 234 tokens to every session, about $0.0009 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
11-testing
Unit, integration, and E2E testing conventions.
webdriver-management
Selenium WebDriver lifecycle management — driver factory, explicit waits, browser options, and teardown.
api-testing
Cypress network interception and API testing patterns (cy.intercept, service mocking, request/response validation).
test-patterns
Selenium pytest test patterns — data-driven tests, fixtures, error handling, and performance checks.
testing-fundamentals
Core Cypress testing principles — selector strategy, smart waiting, and spec organization. Apply when writing or reviewing Cypress E2E tests.
ci-cd
CI/CD pipeline patterns and deployment rules.