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/smeubank/cursor-templateWrote 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/smeubank/cursor-template/monitoring)<a href="https://agentmods.dev/rules/smeubank/cursor-template/monitoring"><img src="https://agentmods.dev/badge/rules/smeubank/cursor-template/monitoring/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/smeubank/cursor-template/monitoring"><img src="https://agentmods.dev/badge/rules/smeubank/cursor-template/monitoring.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.02555 | $0.02555 |
| Opus 5.5 | $0.01022 | $0.01022 |
| Sonnet 5.5 | $0.00511 | $0.00511 |
| Haiku 4.5 | $0.00255 | $0.00255 |
Grade A, and why
monitoring 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 2mo 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 — 451 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monitoring & Observability
🎯 Monitoring Strategy
Comprehensive error tracking and performance monitoring using Sentry with structured logging for both customer and admin experiences.
🔧 Sentry Configuration
Setup
// sentry.client.config.ts
import * as Sentry from '@sentry/nextjs'
Sentry.init({
dsn: process.env.SENTRY_DSN,
environment: process.env.NODE_ENV,
tracesSampleRate: 1.0,
debug: false,
integrations: [
Sentry.browserTracingIntegration(),
],
beforeSend(event, hint) {
// Filter out non-critical errors
if (event.exception) {
const error = hint.originalException
if (error && error.message?.includes('Network Error')) {
return null // Don't send network errors
}
}
return event
},
})
Server Configuration
// sentry.server.config.ts
import * as Sentry from '@sentry/nextjs'
Sentry.init({
dsn: process.env.SENTRY_DSN,
environment: process.env.NODE_ENV,
tracesSampleRate: 1.0,
debug: false,
integrations: [
Sentry.prismaIntegration(),
],
})
📊 Structured Logging Patterns
Core Logging Utility
// lib/logging.ts
import * as Sentry from '@sentry/nextjs'
export interface LogContext {
component: string
action: string
userId?: string
businessId?: string
bookingId?: string
[key: string]: any
}
export function logError(error: Error, context: LogContext) {
Sentry.captureException(error, {
tags: {
component: context.component,
action: context.action,
severity: 'error',
},
extra: {
...context,
timestamp: new Date().toISOString(),
userAgent: typeof window !== 'undefined' ? window.navigator.userAgent : 'server',
},
})
}
export function logInfo(message: string, context: LogContext) {
Sentry.addBreadcrumb({
message,
level: 'info',
category: context.component,
data: context,
})
}
export function logWarning(message: string, context: LogContext) {
Sentry.captureMessage(message, {
level: 'warning',
tags: {
component: context.component,
action: context.action,
},
extra: context,
})
}
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.
- 2mo ago First seen · 451 lines · 2,555 tokens per session scan A 9e46175cb459
monitoring is a cursor rule published in the GitHub repository smeubank/cursor-template (6 stars, last pushed 1y ago), licensed MIT. It adds 2,555 tokens to every session, about $0.0102 per session on Opus 5.5. 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
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.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.