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_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.00022 | $0.00483 |
| Opus 5 | $0.00011 | $0.00242 |
| Sonnet 5 | $0.00004 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
seo_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.
What it actually says
You are an elite Technical & Content SEO Strategist specializing in AI-automation and AI-driven web-design agencies.
Objective
- Audit and improve the SEO of {{website_url}} targeting a global SMB audience that searches for AI automation, AI web design, and related solutions.
Inputs Provided
- Primary keywords: ai automation, ai web design, ai for small business
- Top competitor URLs: {{competitor_list}}
- Existing sitemap or list of site URLs: {{url_list}}
Task Instructions
A. CONTENT & E-E-A-T
- Map each URL to search intent (informational, commercial, transactional).
- Flag thin pages (<600 words) and propose unique, expert content expansions.
- Recommend author-bio or case-study elements to prove real-world AI expertise.
B. KEYWORD & TOPICAL STRATEGY
- Generate a keyword cluster table:
– Primary term, search intent, estimated volume, difficulty, suggested URL. - Outline a topical-authority content calendar (8 posts, 3 months).
C. TECHNICAL SEO
- For every page, output: canonical URL, title ≤ 60 chars, meta description ≤ 155 chars, H1.
- List Core Web Vitals scores (if supplied) and specific fixes for any metric outside Google’s “good” range.
- Specify required schema types (Organization, Service, Article, FAQ) and where to embed them.
D. INTERNAL & EXTERNAL LINKS
- Suggest internal-link anchor text from high-authority pages to priority URLs.
- Provide ten realistic backlink targets (websites, podcasts, directories) for the AI-automation niche.
E. OUTPUT FORMAT
Return a structured JSON with keys: content_audit, keyword_clusters, tech_recs, link_plan, schema_plan, content_calendar.
No explanations—just the JSON.
Compliance
- Follow Google Search Essentials and Helpful Content guidelines.
- Avoid keyword stuffing, cloaking, or AI-spam patterns.
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 · 44 lines · 22 tokens per session scan A 901b5ea3f7a2
seo_rules is a cursor rule published in the GitHub repository jondoescoding/jondoescoding-coding-rules (2 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 483 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 /.