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/proSamik/starterkit-nextjs-aisdk-betterauth-polarWrote 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/prosamik/starterkit-nextjs-aisdk-betterauth-polar/plunk-integration)<a href="https://agentmods.dev/rules/prosamik/starterkit-nextjs-aisdk-betterauth-polar/plunk-integration"><img src="https://agentmods.dev/badge/rules/prosamik/starterkit-nextjs-aisdk-betterauth-polar/plunk-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/prosamik/starterkit-nextjs-aisdk-betterauth-polar/plunk-integration"><img src="https://agentmods.dev/badge/rules/prosamik/starterkit-nextjs-aisdk-betterauth-polar/plunk-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.00922 |
| Opus 5 | $0.00000 | $0.00461 |
| Sonnet 5 | $0.00000 | $0.00184 |
| Haiku 4.5 | $0.00000 | $0.00092 |
Grade A, and why
plunk-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.
This is a copy
100% identical to plunk-integration — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plunk Integration Guide
Overview
Plunk is integrated for user event tracking and analytics. The system tracks authentication-related events including OTP sending, user signups, and password resets.
Core Components
Plunk Client
The main client is in src/lib/plunk/client.ts:
PlunkClientclass with singleton pattern viagetPlunkClient()- Base URL:
https://api.useplunk.com/v1 - Methods:
trackEvent()for analytics,sendEmail()for transactional emails - Automatic API key validation and error handling
Event Tracking Functions
Pre-defined tracking functions in src/lib/plunk/events.ts:
Email Verification OTP
trackEmailVerificationOTP(email: string, otpCode: string)
- Event:
"user-otp" - Subscribed:
false(doesn't affect subscription status) - Data structure:
{ otp: { value: "123456", persistent: false } }
Password Reset OTP
trackPasswordResetOTP(email: string, otpCode: string)
- Event:
"reset-otp" - Subscribed:
false - Data structure:
{ otp: { value: "123456", persistent: false } }
User Signup
trackUserSignup(email: string, fullName?: string)
- Event:
"user-signup" - Subscribed:
true(new users are subscribed by default) - Data structure:
{ fullName: "John Doe" }
Integration Points
Better Auth Server
sendVerificationOTPcallback tracks OTP events automaticallydatabaseHooks.user.create.aftertracks user signups- Non-blocking error handling prevents auth flow interruption
Authentication Pages
Event tracking is integrated into:
- src/app/(auth)/sign-up/page.tsx - User signup tracking
- src/app/(auth)/forgot-password/page.tsx - Password reset tracking
Event Data Standards
OTP Events
All OTP-related events follow this structure:
{
event: "user-otp" | "reset-otp",
email: "[email protected]",
subscribed: false,
data: {
otp: {
value: "123456",
persistent: false
}
}
}
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 · 135 lines · 0 tokens per session scan A f7bb842adc29
plunk-integration is a cursor rule published in the GitHub repository proSamik/starterkit-nextjs-aisdk-betterauth-polar (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 922 tokens. A static security scan graded it A with 0 findings. It is 100% identical to plunk-integration, differing in 0 lines, and is treated as a copy.
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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.