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/brendadeeznuts1111/betting-brain-v3Wrote 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/brendadeeznuts1111/betting-brain-v3/ci-integration)<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.
<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>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.00000 | $0.01303 |
| Opus 5 | $0.00000 | $0.00651 |
| Sonnet 5 | $0.00000 | $0.00261 |
| Haiku 4.5 | $0.00000 | $0.00130 |
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.
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"
}
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.
- 9d ago First seen · 210 lines · 0 tokens per session scan A 5772853822be
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.
Other cursor rules, from other repositories
cloudflare-workers
A deployment and configuration guide for Cloudflare Workers, a platform for running server-side code at Cloudflare's edge. It covers NuxtHub, database choices, Wrangler settings, and two deployment paths.
checker-contract
A rule for designing mechanical checkers and CI gates so their results state exactly what was scanned and whether the scan was complete.
playwright-webserver
A rule for configuring Playwright, a browser-testing tool, so its end-to-end tests can start a web server reliably in continuous integration (CI), where local environment files and tunnels may not exist.
verify-gate-chain
A verification standard that defines an ordered chain of automatic checks, from formatting and type checks through tests and optional health checks.
golden-path-onboarding
An onboarding check for new projects that compares their deployment and CI setup with shared “golden paths,” meaning approved reusable setup patterns.
secrets
A set of rules for storing Cloudflare Workers secrets in GitHub repository secrets and copying them to workers during deployment. Cloudflare Workers are server-side programs that run on Cloudflare’s network.