ci-integration

ci-integration is a cursor rule for Cursor from brendadeeznuts1111/betting-brain-v3. It costs 0 tokens per session (1,303 once invoked), scanned A, original, MIT.

Rules for connecting tests and deployment checks to CI/CD, the automated process that tests and delivers code. They include scheduled GitHub Actions jobs.

In plain words
What is it for?
Use them to configure the main test pipeline, analytics-specific checks, scheduled tests, and Cloudflare deployment validation.
Why use it?
They make testing repeatable in automation and help detect problems through coverage checks, randomized tests, dry-run deployments, and nightly smoke tests.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use them to configure the main test pipeline, analytics-specific checks, scheduled tests, and Cloudflare deployment validation.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/brendadeeznuts1111/betting-brain-v3/ci-integration
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.

Clone the repo
git clone --depth 1 https://github.com/brendadeeznuts1111/betting-brain-v3

Made for: 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.

agentmods badge for ci-integration

README.md
[![agentmods](https://agentmods.dev/badge/rules/brendadeeznuts1111/betting-brain-v3/ci-integration/github.svg)](https://agentmods.dev/rules/brendadeeznuts1111/betting-brain-v3/ci-integration)
Your own site
<a href="https://agentmods.dev/rules/brendadeeznuts1111/betting-brain-v3/ci-integration"><img src="https://agentmods.dev/badge/rules/brendadeeznuts1111/betting-brain-v3/ci-integration/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.

agentmods 80×15 button for ci-integration

Your own site · 80×15
<a href="https://agentmods.dev/rules/brendadeeznuts1111/betting-brain-v3/ci-integration"><img src="https://agentmods.dev/badge/rules/brendadeeznuts1111/betting-brain-v3/ci-integration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,303 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01303
Opus 5 $0.00000 $0.00651
Sonnet 5 $0.00000 $0.00261
Haiku 4.5 $0.00000 $0.00130

Measured 9d ago against content hash 5772853822be, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

ci-integration 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 9d 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.

.cursor/rules/ci-integration.mdc · 210 lines

How it starts

The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CI/CD Integration Rules

Analytics Testing CI Patterns

Main CI Pipeline


// scripts/bun-ci.ts
private async runTests(): Promise<boolean> {
  console.log('🧪 Running tests...');
  
  // Enable AI-friendly output if in AI environment
  if (this.isAIEnvironment()) {
    console.log('  🤖 AI environment detected - enabling quiet mode');
    process.env.CLAUDECODE = '1';
  }

  // Run tests with coverage and randomization for analytics testing
  return await this.runStep(
    'Tests',
    'bun',
    ['test', '--coverage', '--randomize', '--concurrent']
  );
}

Analytics-Specific CI


{
  "analytics:ci": "CI=true bun run analytics:test:coverage"
}

Nightly Analytics Jobs

GitHub Actions Workflow


# .github/workflows/analytics-smoke.yml
name: analytics-smoke
on:
  schedule: [cron: "0 12 * * *"]
jobs:
  smoke:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: oven-sh/setup-bun@v2
      - run: bun install --frozen-lockfile
      - run: wrangler deploy --dry-run
      - run: bun test --test-name-pattern="analytics.*real"
        env:
          CLOUDFLARE_API_TOKEN: ${{ secrets.CF_API_TOKEN }}
          NODE_ENV: staging

Nightly Test Script


// scripts/nightly-analytics-test.ts
export class NightlyAnalyticsTest {
  async run(): Promise<boolean> {
    console.log('🌙 Starting nightly analytics test...');
    
    const dryRunResult = await this.runDryRunTests();
    const smokeTestResult = await this.runSmokeTest();
    
    return dryRunResult.success && smokeTestResult.success;
  }
}

Package.json Scripts

Test Commands

{
  "test": "bun test --randomize",
  "test:coverage": "bun test --coverage --randomize",
  "analytics:test": "bun test tests/unit/analytics-testing-example.test.ts --randomize",
  "analytics:test:coverage": "bun test --coverage --randomize tests/unit/analytics-testing-example.test.ts --config bunfig.analytics.toml",
  "analytics:ci": "CI=true bun run analytics:test:coverage",
  "analytics:nightly": "bun run scripts/nightly-analytics-test.ts",
  "analytics:binding": "bun run scripts/test-analytics-binding.ts"
}

Read the full file on GitHub · 210 lines

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.

  1. 9d ago First seen · 210 lines · 0 tokens per session scan A 5772853822be

Subscribe to this mod's changes

ci-integration is a cursor rule published in the GitHub repository brendadeeznuts1111/betting-brain-v3 (8 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,303 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.