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/MN-Lizard-Team/aiyu-multi-agentWrote 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/mn-lizard-team/aiyu-multi-agent/ci-cd-pipelines)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/ci-cd-pipelines"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/ci-cd-pipelines.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.1 | $0.00010 | $0.01197 |
| Opus 5 | $0.00005 | $0.00598 |
| Sonnet 5 | $0.00002 | $0.00239 |
| Haiku 4.5 | $0.00001 | $0.00120 |
Grade A, and why
ci-cd-pipelines 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 4d 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: ci-cd-pipelines
Cursor Agent-Requested Rule — applied when AI determines relevance.
CI/CD Pipelines - Continuous Integration & Deployment
Automate everything. Fast feedback, reliable releases.
CI/CD Principles
The Pipeline Stages
Code Commit → Build → Test → Security → Deploy → Monitor
│ │ │ │ │ │
▼ ▼ ▼ ▼ ▼ ▼
Linting Compile Unit Scan Staging Health
Formatting Package Integration Audit Prod Metrics
Core Principles
| Principle | Description |
|---|---|
| Fast Feedback | Fail fast, within 10 minutes |
| Repeatable | Same input = same output |
| Isolated | No dependencies on other pipelines |
| Versioned | Pipeline as code, version controlled |
Pipeline Design
GitHub Actions Example
name: CI/CD Pipeline
on:
push:
branches: [main, develop]
pull_request:
branches: [main]
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: '18'
cache: 'npm'
- name: Install dependencies
run: npm ci
- name: Lint
run: npm run lint
- name: Test
run: npm test
- name: Build
run: npm run build
- name: Security audit
run: npm audit --audit-level=moderate
deploy:
needs: build
if: github.ref == 'refs/heads/main'
runs-on: ubuntu-latest
steps:
- name: Deploy to production
run: |
echo "Deploying to production..."
# Deploy commands here
Pipeline Optimization
| Strategy | Implementation |
|---|---|
| Parallel Jobs | Run lint, test, build concurrently |
| Caching | Cache dependencies between runs |
| Conditional Steps | Skip deploy on PRs |
| Artifacts | Pass build artifacts between jobs |
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.
- 4d ago First seen · 215 lines · 10 tokens per session scan A a36f47b28b11
ci-cd-pipelines is a cursor rule published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (7 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 10 tokens to every session and 1,197 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-09-03.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.