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-best-practicesgit 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.00832 | $0.00832 |
| Opus 5 | $0.00416 | $0.00416 |
| Sonnet 5 | $0.00166 | $0.00166 |
| Haiku 4.5 | $0.00083 | $0.00083 |
Grade A, and why
seo-best-practices 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Best Practices for Page Modifications
Core Principles
When modifying any page, ALWAYS prioritize SEO-friendly approaches:
1. Server vs Client Components
- Keep pages as Server Components by default for better SEO
- Only convert to Client Components when absolutely necessary for interactivity
- Hybrid approach: Extract interactive elements into separate Client Components
- Example: Create
ShareButtons.tsxas Client Component, keep main page as Server Component
2. Meta Tags & Structured Data
- Always include comprehensive metadata in page files like app/templates/n8n/page.tsx
- Required meta tags:
title(unique, descriptive, 50-60 characters)description(compelling, 150-160 characters)keywords(relevant, trending terms)- Open Graph tags (
og:title,og:description,og:image,og:url) - Twitter Card tags
- Canonical URLs
- Add JSON-LD structured data for rich snippets
- Use schema.org markup for templates, articles, and services
3. Content Optimization
- H1 tags: One per page, descriptive, includes primary keyword
- H2-H6 hierarchy: Logical structure, includes related keywords
- Content quality: Detailed, valuable, answers user intent
- Internal linking: Link to related pages and services
- Image optimization: Alt text, proper sizing, WebP format when possible
4. URL Structure
- Clean URLs:
/templates/n8n/[slug]format - Descriptive slugs: Include primary keywords
- Breadcrumbs: Clear navigation hierarchy
- Canonical URLs: Prevent duplicate content issues
5. Performance & Core Web Vitals
- Lazy loading: Non-critical components and images
- Code splitting: Separate Client Components
- ISR (Incremental Static Regeneration): Use
revalidatefor dynamic content - Minimize JavaScript: Keep client-side code minimal
6. Technical SEO Checklist
Before modifying any page, ensure:
- Meta tags are complete and optimized
- Structured data is implemented
- Page loads server-side rendered content
- Interactive elements are isolated in Client Components
- URLs follow SEO-friendly patterns
- Content includes target keywords naturally
- Internal linking strategy is maintained
- Images have proper alt text
- Page performance remains optimal
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 · 74 lines · 832 tokens per session scan A baab371ce376
seo-best-practices is a cursor rule published in the GitHub repository jondoescoding/jondoescoding-coding-rules (2 stars, last pushed 1mo ago), licensed MIT. It adds 832 tokens to every session, about $0.0042 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 /.