Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/brendadeeznuts1111/betting-brain-v3npx agentmods add rules/brendadeeznuts1111/betting-brain-v3/analytics-stub-apiWrote 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/analytics-stub-api)<a href="https://agentmods.dev/rules/brendadeeznuts1111/betting-brain-v3/analytics-stub-api"><img src="https://agentmods.dev/badge/rules/brendadeeznuts1111/betting-brain-v3/analytics-stub-api/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/analytics-stub-api"><img src="https://agentmods.dev/badge/rules/brendadeeznuts1111/betting-brain-v3/analytics-stub-api.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.01618 |
| Opus 5 | $0.00000 | $0.00809 |
| Sonnet 5 | $0.00000 | $0.00324 |
| Haiku 4.5 | $0.00000 | $0.00162 |
Grade A, and why
analytics-stub-api 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AnalyticsEngineStub API Rules
Core Interface
AnalyticsCall Interface
export interface AnalyticsCall {
blobs: string[];
doubles: number[];
tags?: Record<string, string>;
timestamp: number;
}
AnalyticsEngineStub Class
export class AnalyticsEngineStub {
private calls: AnalyticsCall[] = [];
private flushPromises: Promise<void>[] = [];
async writeDataPoint(data: {
blobs: string[];
doubles: number[];
tags?: Record<string, string>;
}): Promise<void> {
// Implementation
}
}
Core Methods
writeDataPoint
// ✅ CORRECT: Standard analytics call
await analytics.writeDataPoint({
blobs: ['event_type', 'data_type'],
doubles: [1.5, 1000],
tags: { source: 'test', version: '1.0' }
});
getCalls
// ✅ CORRECT: Get all calls
const calls = analytics.getCalls();
expect(calls).toHaveLength(1);
expect(calls[0].blobs).toEqual(['event_type', 'data_type']);
callCount
// ✅ CORRECT: Count calls
expect(analytics.callCount()).toBe(1);
Filtering Methods
callsWithBlob
// ✅ CORRECT: Filter by blob content
const eventCalls = analytics.callsWithBlob('event_type');
expect(eventCalls).toHaveLength(1);
callsWithTag
// ✅ CORRECT: Filter by tag
const sourceCalls = analytics.callsWithTag('source', 'test');
expect(sourceCalls).toHaveLength(1);
wasCalledWith
// ✅ CORRECT: Check specific call
expect(analytics.wasCalledWith({
blobs: ['event_type', 'data_type'],
doubles: [1.5, 1000]
})).toBe(true);
Utility Methods
clearCalls
// ✅ CORRECT: Clear all calls
analytics.clearCalls();
expect(analytics.callCount()).toBe(0);
getStats
// ✅ CORRECT: Get call statistics
const stats = analytics.getStats();
expect(stats.totalCalls).toBe(1);
expect(stats.averageDoublesPerCall).toBe(2);
flush
// ✅ CORRECT: Flush analytics (auto-called)
analytics.flush();
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 · 277 lines · 0 tokens per session scan A 6d28aa60e8cd
analytics-stub-api 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,618 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
workflow-deployment
Workflow testing and deployment process guide.
writing-tests
How to write tests in the monorepo.
manual-review
The main set of rules for manual review during an active project change. It defines different kinds of checks, who performs them, how results are recorded, and when supporting evidence is required.
testing-anti-patterns
Guidelines for avoiding misleading or weak tests. They say tests should check real application behavior, use mocks only when needed for isolation, and avoid adding code to production solely for testing.
manual-review.data-readiness
A set of rules for preparing manual checks before a proposed change is implemented. It requires each user-facing check to include exact sample data, clear steps, and any needed setup.
manual-review.evidence
A set of rules for writing and reviewing the evidence section of a task list. It defines a consistent checklist format and explains how to describe a user action together with the result that should follow.