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/hamzaamjad/cursor-rules/435-ci-cd-testing-gatekeepergit clone --depth 1 https://github.com/hamzaamjad/cursor-rulesWhat 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.00000 | $0.00163 |
| Opus 5 | $0.00000 | $0.00081 |
| Sonnet 5 | $0.00000 | $0.00033 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
435-ci-cd-testing-gatekeeper 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 2d 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-testing-gatekeeper
Purpose: Enforce quality and reliability via CI/CD.
- Every PR must pass:
- Linting (code style), formatting, and static typing checks.
- Unit tests with ≥ 80% coverage; report coverage.
- Security scan (e.g., Snyk, Dependabot alerts). Include guidelines for integrating new CI/CD tools and practices.
- Define checks in pipeline config (GitHub Actions, GitLab CI, etc.).
- Require at least one approving review before merge. Regularly update test suites to cover new features and edge cases.
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.
- 2d ago First seen · 17 lines · 0 tokens per session scan A 0a4537778499
435-ci-cd-testing-gatekeeper is a cursor rule published in the GitHub repository hamzaamjad/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 163 tokens. 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 cursor rules, from other repositories
40-deploy
For PM2 processes, GitHub Actions, health checks, and production operations.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
workflow-ci
Testing and verification workflow expectations.
ci-scripts-maintenance
CI and script maintenance after software updates.
test-headless-github-actions
Run Maven tests with GITHUBACTIONS=true so @WebTest Chrome is headless.
cursorrules
When the user asks about ci cd generator, use ci-cd-generator-ai-mcp tools: generatepipeline, validateconfig, listtemplates, optimizestages.