A pre-release checking process that runs type checks, code-quality checks, a build, tests, and a security review in order.

Use it before releasing major changes or opening a pull request to find type errors, lint problems, build failures, test failures, and critical security findings.

It gathers common shipping checks into one repeatable gate and stops early when a broken build makes later checks unreliable.

pipeline — Cursor rule for coding agents by Jkudjo: A pre-release checking process that runs type checks, code-quality…

Install

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.

agentmods

npx agentmods add rules/jkudjo/oh-my-cursor/pipeline

Clone the repo

git clone --depth 1 https://github.com/Jkudjo/oh-my-cursor

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/jkudjo/oh-my-cursor/pipeline.svg)](https://agentmods.dev/rules/jkudjo/oh-my-cursor/pipeline)

Your own site

<a href="https://agentmods.dev/rules/jkudjo/oh-my-cursor/pipeline"><img src="https://agentmods.dev/badge/rules/jkudjo/oh-my-cursor/pipeline.svg" alt="Measured on agentmods" height="20"></a>

Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 506 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00016	$0.00506
Opus 5	$0.00008	$0.00253
Sonnet 5	$0.00003	$0.00101
Haiku 4.5	$0.00002	$0.00051

Measured 5d ago against content hash 73b6e2e0776b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pipeline 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.

rules/pipeline.mdc · 55 lines

What it actually says

@pipeline

Trigger: Before shipping, after major changes, or as a pre-PR gate.

Stages (run in order, stop on critical failure)

Stage	Command hint	Fail condition
1. Typecheck	`tsc --noEmit` / `pyright`	Any type errors
2. Lint	`eslint` / `biome` / `ruff`	Errors (warnings OK)
3. Build	`npm run build` / `cargo build`	Non-zero exit
4. Tests	`npm test` / `pytest`	Any failures
5. Security scan	Run `@security-review` inline	Any CRITICAL findings

Protocol

Call start_mode mode=autopilot task=pipeline (reuse for tracking).
Run each stage in sequence. For each stage:
- Execute the relevant command
- Check result
- Call update_mode_state with phase=stage-N
- If FAIL: attempt one auto-fix cycle (same as @qa cycle mode)
- If still FAIL after one cycle: mark stage as failed, continue to next (unless critical)
Stop entirely if build fails (no point running tests against a broken build).
Run @security-review as final stage — flag CRITICAL findings.

Write pipeline report:

## Pipeline Report

| Stage | Result | Cycles used |
|-------|--------|-------------|
| Typecheck | ✓ PASS | 0 |
| Lint | ✓ PASS | 1 (auto-fixed) |
| Build | ✓ PASS | 0 |
| Tests | ✗ FAIL | 1 |
| Security | ✓ PASS | — |

**Overall: PASS / FAIL**
Issues remaining: ...

Call save_artifact type=specs, slug=pipeline-{date}.
Call update_mode_state status=completed.

Rules

Fix auto-fixable issues (lint, simple type errors) automatically.
Never modify tests to make them pass.
A pipeline PASS with security CRITICAL is still a FAIL.

Changes

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 · 55 lines · 16 tokens per session scan A 73b6e2e0776b

Subscribe to this mod's changes

pipeline is a cursor rule published in the GitHub repository Jkudjo/oh-my-cursor (1 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 506 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-08-31.

CI and CD DevOps and cloud agent ai-workflow codex cursor cursor-ai cursor-rules

pipeline

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

@pipeline

Stages (run in order, stop on critical failure)

Protocol

Rules

What this file has done since we first saw it

Other cursor rules, from other repositories

turborepo

ci-cd

code-optimization

ci-cd

release

implementation-workflow