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.
npx agentmods add rules/jondoescoding/jondoescoding-coding-rules/seo-google-rulesgit clone --depth 1 https://github.com/jondoescoding/jondoescoding-coding-rulesWhat 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 | $0.00017 | $0.05162 |
| Opus 5 | $0.00009 | $0.02581 |
| Sonnet 5 | $0.00003 | $0.01032 |
| Haiku 4.5 | $0.00002 | $0.00516 |
Grade A, and why
seo-google-rules 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 yesterday.
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 — 770 lines — stays where its author put it; the contents beside it link to each section on GitHub.
13. Monitoring & Testing
SEO Checklist for Every Page
- Unique title tag (50-60 characters)
- Meta description (150-160 characters)
- One H1 tag with target keyword
- Proper heading hierarchy (H1 → H2 → H3)
- Alt text for all images
- [ ]# SEO-Optimized Cursor Rules for Next.js Business Website
Project Context
You are developing a SEO-optimized business website using Next.js 15+, React 19, Tailwind CSS, and MongoDB. Follow Google's SEO Starter Guide principles strictly. Prioritize technical SEO and mobile-first development. This project uses the App Router architecture.
Core SEO Principles
1. Technical SEO Foundation
- Always use semantic HTML5 elements (
<header>,<nav>,<main>,<article>,<section>,<aside>,<footer>) - Implement proper heading hierarchy - Only one
<h1>per page, followed by<h2>,<h3>in logical order - Generate XML sitemaps automatically using
next-sitemappackage - Create robots.txt with proper directives
- Implement canonical URLs to prevent duplicate content issues
- Use Server-Side Rendering (SSR) or Static Site Generation (SSG) for all public pages
2. Next.js SEO Implementation
Metadata API Usage (Next.js 15)
// Always use Next.js 15 Metadata API for SEO
import type { Metadata } from 'next';
export const metadata: Metadata = {
title: 'Page Title - Business Name',
description: 'Compelling description under 160 characters that includes target keywords naturally',
keywords: ['relevant', 'keywords', 'for', 'SEO'],
authors: [{ name: 'Author Name' }],
creator: 'Business Name',
publisher: 'Business Name',
formatDetection: {
email: false,
address: false,
telephone: false,
},
metadataBase: new URL('https://yourdomain.com'),
openGraph: {
title: 'Page Title - Business Name',
description: 'Compelling description for social sharing',
url: 'https://yourdomain.com/current-page',
siteName: 'Business Name',
images: [
{
url: '/og-image.jpg',
width: 1200,
height: 630,
alt: 'Descriptive alt text for OG image',
}
],
locale: 'en_US',
type: 'website',
},
twitter: {
card: 'summary_large_image',
title: 'Page Title - Business Name',
description: 'Compelling description for Twitter',
creator: '@yourtwitterhandle',
images: ['/twitter-image.jpg'],
},
alternates: {
canonical: 'https://yourdomain.com/current-page',
languages: {
'en-US': 'https://yourdomain.com/en-US',
'es-ES': 'https://yourdomain.com/es-ES',
},
},
robots: {
index: true,
follow: true,
nocache: true,
googleBot: {
index: true,
follow: true,
'max-video-preview': -1,
'max-image-preview': 'large',
'max-snippet': -1,
},
},
verification: {
google: 'google-site-verification-code',
yandex: 'yandex-verification-code',
yahoo: 'yahoo-verification-code',
},
};
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.
- yesterday First seen · 770 lines · 17 tokens per session scan A de99f68004b2
seo-google-rules is a cursor rule published in the GitHub repository jondoescoding/jondoescoding-coding-rules (2 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 5,162 once invoked, about $0.0001 per session on Opus 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
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
app-router-patterns
Next.js 14+ App Router patterns — Server Components, Client Components, Route Handlers, Server Actions, and metadata API.
test-patterns
Selenium pytest test patterns — data-driven tests, fixtures, error handling, and performance checks.
testing-fundamentals
Core Cypress testing principles — selector strategy, smart waiting, and spec organization. Apply when writing or reviewing Cypress E2E tests.
new_features
Guidelines for integrating new features into the Task Master CLI.
utilities
// ✅ DO: Create focused, reusable utilities /.