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/oakensoul/nextjs-cursor-promptsWrote 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/oakensoul/nextjs-cursor-prompts/component-update-marketing)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/component-update-marketing"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/component-update-marketing/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/oakensoul/nextjs-cursor-prompts/component-update-marketing"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/component-update-marketing.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.05008 |
| Opus 5 | $0.00000 | $0.02504 |
| Sonnet 5 | $0.00000 | $0.01002 |
| Haiku 4.5 | $0.00000 | $0.00501 |
Grade A, and why
component-update-marketing 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 — 741 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Marketing Component Update Request
Please enhance the existing marketing component with conversion optimization, performance improvements, advanced analytics integration, and A/B testing capabilities.
🎯 MARKETING UPDATE OBJECTIVES:
- OPTIMIZE conversion rates with improved messaging, CTA placement, and user journey optimization
- ENHANCE performance with Core Web Vitals improvements, image optimization, and loading speed
- IMPLEMENT advanced analytics with detailed tracking, user behavior analysis, and conversion funnel monitoring
- ADD A/B testing capabilities with variant management, statistical significance tracking, and result analysis
- MAINTAIN brand consistency while implementing data-driven improvements and personalization
📋 MARKETING ENHANCEMENT METHODOLOGY:
STEP 1: Current Marketing Component Assessment
Conversion Analysis:
- Current conversion rates: Baseline metrics for CTAs, form submissions, and user actions
- User journey mapping: Identify friction points and optimization opportunities
- Message effectiveness: Analyze headline, copy, and value proposition performance
- CTA performance: Review click-through rates and conversion attribution
Performance Audit:
- Core Web Vitals: Analyze LCP, FID, CLS scores for marketing pages
- Image optimization: Review image sizes, formats, and loading strategies
- Bundle analysis: Identify opportunities for code splitting and lazy loading
- Mobile performance: Assess mobile-specific performance bottlenecks
Analytics Review:
- Tracking completeness: Verify all marketing interactions are tracked
- Data quality: Ensure accurate attribution and event tracking
- Funnel analysis: Identify conversion funnel drop-off points
- User behavior: Review heatmaps, scroll depth, and engagement metrics
STEP 2: Conversion Rate Optimization (CRO)
Advanced CTA Optimization:
// Enhanced CTA with conversion tracking and optimization
const OptimizedCTA = ({
config,
position,
testVariant,
urgency = false,
personalizedText
}) => {
const { trackCTAClick, trackCTAView } = useConversionTracking()
const [isVisible, setIsVisible] = useState(false)
const ctaRef = useRef(null)
// Track CTA visibility for conversion analysis
useEffect(() => {
const observer = new IntersectionObserver(
([entry]) => {
if (entry.isIntersecting && !isVisible) {
setIsVisible(true)
trackCTAView({
position,
variant: testVariant,
urgency,
timestamp: new Date().toISOString()
})
}
},
{ threshold: 0.5 }
)
if (ctaRef.current) {
observer.observe(ctaRef.current)
}
return () => observer.disconnect()
}, [isVisible, position, testVariant, urgency, trackCTAView])
const handleClick = () => {
trackCTAClick({
text: personalizedText || config.text,
position,
variant: testVariant,
urgency,
timeToClick: performance.now() - pageLoadTime,
scrollDepth: getScrollDepth()
})
if (config.onClick) {
config.onClick()
}
}
return (
<motion.button
ref={ctaRef}
className={cn(
"cta-button",
`cta-${config.variant}`,
`cta-${config.size}`,
urgency && "cta-urgent",
testVariant && `cta-variant-${testVariant}`
)}
onClick={handleClick}
whileHover={{ scale: 1.05 }}
whileTap={{ scale: 0.95 }}
data-testid={`cta-${position}`}
>
{urgency && (
<span className="cta-urgency-indicator">
🔥
</span>
)}
{personalizedText || config.text}
</motion.button>
)
}
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 · 741 lines · 0 tokens per session scan A 322dbc0b3f2f
component-update-marketing is a cursor rule published in the GitHub repository oakensoul/nextjs-cursor-prompts (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,008 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
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.