plunk-integration

plunk-integration is a cursor rule for Cursor from proSamik/starterkit-nextjs-aisdk-betterauth-polar. It costs 0 tokens per session (922 once invoked), scanned A, a copy of plunk-integration, MIT.

Documentation for tracking authentication-related events and analytics with Plunk, an email and event-tracking service.

In plain words
What is it for?
Use it when working with the Plunk client or adding and checking event tracking for authentication flows.
Why use it?
It explains how the application records events such as one-time password messages, signups, and password resets.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when working with the Plunk client or adding and checking event tracking for authentication flows.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/prosamik/starterkit-nextjs-aisdk-betterauth-polar/plunk-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/proSamik/starterkit-nextjs-aisdk-betterauth-polar

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 plunk-integration

README.md
[![agentmods](https://agentmods.dev/badge/rules/prosamik/starterkit-nextjs-aisdk-betterauth-polar/plunk-integration/github.svg)](https://agentmods.dev/rules/prosamik/starterkit-nextjs-aisdk-betterauth-polar/plunk-integration)
Your own site
<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.

agentmods 80×15 button for plunk-integration

Your own site · 80×15
<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>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 922 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 100% copy Near-identical to another mod 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.00922
Opus 5 $0.00000 $0.00461
Sonnet 5 $0.00000 $0.00184
Haiku 4.5 $0.00000 $0.00092

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

Security

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.

Origin

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.

.cursor/rules/plunk-integration.mdc · 135 lines

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:

  • PlunkClient class with singleton pattern via getPlunkClient()
  • 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

In src/lib/auth/server.ts:

  • sendVerificationOTP callback tracks OTP events automatically
  • databaseHooks.user.create.after tracks user signups
  • Non-blocking error handling prevents auth flow interruption

Authentication Pages

Event tracking is integrated into:

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
    }
  }
}

Read the full file on GitHub · 135 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 · 135 lines · 0 tokens per session scan A f7bb842adc29

Subscribe to this mod's changes

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.